We're a group of makers shipping together. We help each other stay accountable and reach our goals.
Apply for access
So easy ^^
I had to laugh at your comment @carolinus because I think I knew 5 words in Nik's comment and understood nothing. 😆
There are regular people and then there are coders/developers.
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.sqlite and 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 @carolinus because I think I knew 5 words in Nik's comment and understood nothing. 😆
There are regular people and then there are coders/developers.
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 model here?
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.sqlite and 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 @carolinus because I think I knew 5 words in Nik's comment and understood nothing. 😆
There are regular people and then there are coders/developers.
It's clearly a key figure. I'll keep that in mind.
It seems that many of you install brew first. Maybe I should read his doc again :)
anything else?
Already felt like I was cheating with 2 "first" installs, but @jefftriplett is right: 1Password (homebrew is included in rails.new).
In the right?
Mostly, in the center bottom :)