Provide a fast, easily accessible, development server

[elia]

Description This is intended for when a fast development cycle or manual inspection is needed, the server starts in a handful of seconds and leaves no traces.

• the DB is an in-memory SQLite
• logs are sent to STDOUT
• defaults to port 3000
• easy access to /admin with a dummy admin-user (pre signed-in)
• easy to discover with bin/server
• compatible with puma-dev

Checklist:

• [x] I have followed Pull Request guidelines
• [x] I have added a detailed description into each commit message
• [ ] I have updated Guides and README accordingly to this change (if needed)
• [ ] I have attached screenshots to this PR for visual changes (if needed)

with puma-dev

[spaghetticode]

@elia this is a great idea! I wonder if we could make the FE fully usable as well somehow, but I guess the effort would not be small.

[elia]

@tvdeyen thanks for the review, I've followed your suggestions! @spaghetticode I've updated the code, it now has two additional routes that will load seeds and samples: localhost:3000/solidus/seed and ~localhost:3000/solidus/load_samples~ localhost:3000/solidus/samples, that way they can be run depending on the situation.

Also Paperclip is kept in memory as much as possible (identify and convert still use tempfiles(

[kennyadsl]

@elia thanks, this is great. I have a final question: do you think it's worth mentioning somewhere in guides or in the README?

[elia]

@kennyadsl @tvdeyen you think this could still be helpful? The sandbox improved a lot since 2019, it's easy to regenerate, and conveniently responds to bin/rails commands, but there might still be some use cases for this.

Please let me know and I can extract the first commit to a different PR if needed, or add info to the readme if we want to merge it.

[tvdeyen]

@kennyadsl @tvdeyen you think this could still be helpful? The sandbox improved a lot since 2019, it's easy to regenerate, and conveniently responds to bin/rails commands, but there might still be some use cases for this.

Please let me know and I can extract the first commit to a different PR if needed, or add info to the readme if we want to merge it.

@elia bare with me, but this has been a while. Can you elaborate what would be the benefit compared to the sandbox? Is it just for "don't need a sandbox"? If the sandbox already provides anything we need as a fast local dev server I would like to reduce the maintenance burden of maintaining two dev environments, although I really appreciate the effort put into this.

[elia]

@tvdeyen yeah, I think a bunch of things from this actually ended up in the sandbox, I just wanted to be sure I was not gonna close this if it had a legit use case (looks like there isn't), and the double maintenance is a great point 👍

[tvdeyen]

👍🏻