An unnamed cloud storage app
This repository has been archived on 2024-07-19. You can view files and clone it, but cannot push or open issues or pull requests.
Find a file
2023-12-18 00:05:39 -05:00
.github/workflows ci(backend): stop building dev images in CI 2023-12-16 21:08:19 -05:00
assets chore: add logo to README (#20) 2023-08-16 13:49:24 -04:00
backend refactor(taskfiles): consolidate start+stop, add namespace for docker tasks 2023-12-18 00:02:04 -05:00
frontend refactor(frontend): queries > hooks, consolidate useFileMutations (#24) 2023-08-18 21:07:00 -04:00
script feat(backend): sub fetch endpoints (#2) 2023-08-08 23:49:54 -04:00
.gitignore refactor: FastAPI -> Django migration (#41) 2023-11-26 21:34:09 -05:00
backend-test.env refactor(taskfiles): extract start logic out of taskfile 2023-12-18 00:01:26 -05:00
LICENSE chore: add AGPLv3 license 2023-08-17 21:20:02 -04:00
README.md chore: add logo to README (#20) 2023-08-16 13:49:24 -04:00
renovate.json5 chore: Configure Renovate (#43) 2023-11-26 21:50:28 -05:00
Taskfile.backend.yml refactor(taskfiles): consolidate start+stop, add namespace for docker tasks 2023-12-18 00:02:04 -05:00
Taskfile.frontend.yml fix: trigger ci run if taskfile changes + split basepath env variable… (#27) 2023-08-19 11:33:18 -04:00
Taskfile.yml refactor(taskfiles): remove redundant paths and venv entries in backend taskfile 2023-12-18 00:02:04 -05:00

Rotini

Overview

Rotini is a self-hosted cloud storage application that gives you full-control over the data you store. It aims for simplicity and extensibility, such that you can get started in minutes and easily fork or contribute upstream if you fancy a feature that's not already there.

It's roadmap is currently TBD and will become better defined as it gets closer to a first release.

Development

Tooling

Utility commands are managed by go-task and can be called from anywhere. Running . script/bootstrap installs go-task within the project and gets everything ready. From there, task -l provides a breakdown of available tools.

Note that this is the preferred way to running any tooling-related task within the repository, regardless of environment.

Running locally

The application requires a Postgres database instance to be made available to the backend. This can be done for you via task be:start-db.

Starting the backend and frontend applications can be done via task be:start and task fe:start.

Starting the backend application

The backend application is available as a container, which you can run as

task be:start

If you opt to run your database in an adjacent container, you can either run containers in such a manner than they share a network or define the database's host via docker.host.internal:

task be:start -- --add-host docker.host.internal:host-gateway

More generally, extra options can be passed to the docker run call that runs the application this way:

task be:start -- <options>

See the README files of each of those environments (backend, frontend) for specific requirements.)