No description
eeacaca725
The Docker build wasn't making use of docker's cache because the .git directory was being copied into the build context. This means that even if the app did not change, if anything in git changed then docker would rebuild the entire app. This excludes the .git folder from the docker build, instead relying on the user to pass in the build hash at build time. Which is annoying but I don't think there's a better way around it. This was annoying me because I am deploying a self-hosted version of flotilla from a git branch via ansible and it was rebuilding flotilla every time. Co-authored-by: mplorentz <mplorentz@noreply.gitea.coracle.social> Reviewed-on: https://gitea.coracle.social/coracle/flotilla/pulls/88 Co-authored-by: Matt Lorentz <mplorentz@noreply.coracle.social> Co-committed-by: Matt Lorentz <mplorentz@noreply.coracle.social> |
||
|---|---|---|
| .gitea/workflows | ||
| .husky | ||
| android | ||
| assets | ||
| ios | ||
| src | ||
| src-tauri | ||
| static | ||
| .ackrc | ||
| .dockerignore | ||
| .env.local | ||
| .env.template | ||
| .fdignore | ||
| .gitattributes | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| AGENTS.md | ||
| build-in-production.sh | ||
| build.sh | ||
| capacitor.config.ts | ||
| CHANGELOG.md | ||
| Dockerfile | ||
| eslint.config.js | ||
| LICENSE | ||
| link_deps | ||
| package.json | ||
| pnpm-lock.yaml | ||
| postcss.config.js | ||
| pwa-assets.config.js | ||
| README.md | ||
| rust-toolchain.toml | ||
| svelte.config.js | ||
| tailwind.config.js | ||
| tsconfig.json | ||
| vite.config.ts | ||
| zapstore.yaml | ||
Flotilla
A discord-like nostr client based on the idea of "relays as groups".
If you would like to be interoperable with Flotilla, please check out this guide: https://habla.news/u/hodlbod@coracle.social/1741286140797
Environment
You can also optionally create an .env file and populate it with the following environment variables (see .env for examples):
VITE_DEFAULT_PUBKEYS- A comma-separated list of hex pubkeys for bootstrapping web of trustVITE_PLATFORM_URL- The url where the app will be hostedVITE_PLATFORM_NAME- The name of the appVITE_PLATFORM_LOGO- A logo url for the app. Can be a local path or https link. Must be a PNG file.VITE_PLATFORM_RELAYS- A list of comma-separated relay urls that will make flotilla operate in "platform mode". Disables all space browse/add/select functionality and makes the first platform relay the home page.VITE_PLATFORM_ACCENT- A hex color for the app's accent colorVITE_PLATFORM_DESCRIPTION- A description of the app
If you're deploying a custom version of flotilla, be sure to remove the plausible.coracle.social script from app.html. This sends analytics to a server hosted by the developer.
Development
See CONTRIBUTING.md.
Deployment
To run your own Flotilla, it's as simple as:
pnpm install
pnpm run build
npx serve build
Or, if you prefer to use a container:
podman run -d -p 3000:3000 ghcr.io/coracle-social/flotilla:latest
Alternatively, you can copy the build files into a directory of your choice and serve it yourself:
mkdir ./mount
podman run -v ./mount:/app/mount ghcr.io/coracle-social/flotilla:latest bash -c 'cp -r build/* mount'