rotini/README.md

# rotini
An unnamed cloud storage app

## Development

### Tooling

Utility commands are managed by [go-task](https://github.com/go-task/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

```sh
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`:

```sh
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:

```sh
task be:start -- <options>
```

See the README files of each of those environments ([backend](./backend/README.md), [frontend](./frontend/README.md)) for specific requirements..
Initial commit 2023-08-05 16:06:32 +00:00			`# rotini`
			`An unnamed cloud storage app`
feat(backend): sub fetch endpoints (#2) * feat(backend): sub fetch endpoints * ci: skip frontend/backend if no frontend change * ci: backend formatting * build: tooling and commands * build: psycopg2 * build: dependency locking tooling * build: pylint * feat: migration handling * feat: rudimentary upload flow * feat: basic file create/read interactions * docs: stubs * build: migration command 2023-08-09 03:49:54 +00:00
			`## Development`

build: tooling clean-up (#14) * build(backend): requirements-locks to use venv directly to avoid needing to activate * build(backend): taskfile cleaning, no more sourcing * build(frontend): remove unneeded syntax, cmds>cmd for one-liners * docs: instructors on local setup * ci: hoisted default working directory settings 2023-08-12 20:32:07 +00:00			`### Tooling`

			Utility commands are managed by [go-task](https://github.com/go-task/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`.

build(backend): run as a container (#17) * docs: document running as a container * build: functional dockerfile * build: task command tweaks to accommodate docker app * ci(backend): optionally build dev docker image 2023-08-16 03:57:09 +00:00			`#### Starting the backend application`

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

			```sh
			`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`:

			```sh
			`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:

			```sh
			`task be:start -- <options>`
			```

			`See the README files of each of those environments ([backend](./backend/README.md), [frontend](./frontend/README.md)) for specific requirements..`