Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The backend code should be built and pushed with couchdb-push instead of couchapp #198

Open
benel opened this issue Jun 6, 2024 · 1 comment
Labels

Comments

@benel
Copy link
Member

benel commented Jun 6, 2024

Among other reasons, the idea would be to use less disk space on developers' (esp. students') computers.

couchapp container couchdb-push
900 MB 21 MB
@benel benel added the process label Jun 6, 2024
@benel benel changed the title The backend code should be built with grunt-couch or couchdb-push instead of couchapp The backend code should be built with couchdb-push instead of couchapp Jun 6, 2024
@benel benel changed the title The backend code should be built with couchdb-push instead of couchapp The backend code should be built and pushed with couchdb-push instead of couchapp Jun 6, 2024
@benel
Copy link
Member Author

benel commented Jun 6, 2024

For the design document

Add a file named _id in backend/srcwith the following content:

_design/app

Then you can push the backend code with:

npx couchdb-push http://TO_BE_CHANGED:TO_BE_CHANGED@localhost:5984/my-app backend/src

For samples

You can push all sample documents with:

for f in samples/* ; npx couchdb-push http://TO_BE_CHANGED:TO_BE_CHANGED@localhost:5984/my-app $f

But this is really slow!
It seems that it could be replaced:

  • with couchdb-bootstrap (from the same software suite) but with adaptations,
  • with putdoc directly (with the --docs option).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant