Some features I worked on for #toyboxforlaravel (similar project) before reducing its scope also were:
- Documentation generation
- User feedback/testimonials & roadmap management (data model for these overlaps a lot so I lumped it all together)
- Database backup initiation/download (very easy to do with SQLite, with other DBs less so)
Also useful might be some basic application health metrics (depends on if this is intended to be hosted on a VPS or with serverless).
I'm working with Laravel here, which is very batteries-included with this sort of thing.
For the SQLite DB setup, my init script does a touch database/db_name.sqlite and then the DB migrations I've written (laravel.com/docs/11.x/migrati…) can be run on this DB.
Some features I worked on for
#toyboxforlaravel (similar project) before reducing its scope also were:
- Documentation generation
- User feedback/testimonials & roadmap management (data model for these overlaps a lot so I lumped it all together)
- Database backup initiation/download (very easy to do with SQLite, with other DBs less so)
Also useful might be some basic application health metrics (depends on if this is intended to be hosted on a VPS or with serverless).
Some of your ideas sounds like very great!
How do you manage your model for a new installation? copy paste?
What do you mean with
modelhere?The project is setup as a github repo template, plus some basic bash scripts for setting up some common items.
I mean how do you create your database? I assume you have a json stored somewhere?
I'm working with Laravel here, which is very batteries-included with this sort of thing.
For the SQLite DB setup, my init script does a
touch database/db_name.sqliteand then the DB migrations I've written (laravel.com/docs/11.x/migrati…) can be run on this DB.So easy ^^
I had to laugh at your comment @karlondavis because I think I knew 5 words in Nik's comment and understood nothing. 😆
There are regular people and then there are coders/developers.
Lol for sure ^^