bewCloud

This is the bewCloud app built using Fresh and deployed using docker compose.

[!CAUTION] This is actively being built and should be considered pre-alpha. Bugs will exist. Code and models can change without a good upgrade path (though I'll try to avoid that). Don't use it as your only source of data!

Self-host it!

Download/copy docker-compose.yml and .env.sample as .env.

$ docker compose up # makes the app available at http://localhost:8000
$ docker compose run website bash -c "cd /app && make migrate-db" # initializes/updates the database (only needs to be executed the first time and on any updates)

Alternatively, check the Development section below.

[!IMPORTANT] Even with signups disabled (CONFIG_ALLOW_SIGNUPS="false"), the first signup will work and become an admin.

Requirements

This was tested with Deno's version stated in the .dvmrc file, though other versions may work.

For the postgres dependency (used when running locally or in CI), you should have Docker and docker compose installed.

Don't forget to set up your .env file based on .env.sample.

Development

$ docker compose -f docker-compose.dev.yml up # (optional) runs docker with postgres, locally
$ make migrate-db # runs any missing database migrations
$ make start # runs the app
$ make format # formats the code
$ make test # runs tests

Other less-used commands

$ make exec-db # runs psql inside the postgres container, useful for running direct development queries like `DROP DATABASE "bewcloud"; CREATE DATABASE "bewcloud";`
$ make build # generates all static files for production deploy

Structure

• Routes defined at routes/.
• Static files are defined at static/.
• Static frontend components are defined at components/.
• Interactive frontend components are defined at islands/.
• Cron jobs are defined at crons/.
• Reusable bits of code are defined at lib/.
• Database migrations are defined at db-migrations/.

Deployment

Just push to the main branch.

Tentative Roadmap for a v1 beta:

• Dashboard with URLs and Notes
• News
• Files UI
• WebDav Server
• Desktop app for selective file sync (rclone via WebDav)
• Mobile app for offline file view (API + WebDav client)
• Add photo auto-uplod support for mobile client
• Add notes view support for mobile app
• Add notes edit support for mobile app
• Notes UI
• Photos UI

Where's Contacts/Calendar (CardDav/CalDav)?! Wasn't this supposed to be a core Nextcloud replacement?

Check this tag/release for more info and the code where/when that was being done. Contacts/CardDav worked and Calendar/CalDav mostly worked as well at that point.

My focus is still to get me to replace Nextcloud for me and my family ASAP, but turns out it's not easy to do it all in a single, installable thing, so I'm focusing on the Files UI, sync, and sharing, since Radicale solved my other issues better than my own solution (and it's already very efficient).

How does file sharing work?

Check this PR for advanced sharing with internal and external users, with read and write access that was being done and almost working. I ditched all that complexity for simply using symlinks, as it served my use case (I have multiple data backups and trust the people I provide accounts to, with the symlinks).

You can simply ln -s /<absolute-path-to-data-files>/<owner-user-id>/<directory-to-share> /<absolute-path-to-data-files>/<user-id-to-share-with>/ to create a shared directory between two users, and the same directory can have different names, now.

[!NOTE] If you're running the app with docker, the symlink needs to point to the container's directory, usually starting with /app if you didn't change the Dockerfile, otherwise the container will fail to load the linked directory.