flatcar-rails / flatcar Goto Github PK

It would be helpful for someone to document the workflow for using Flatcar starting at nothing and ending up with a complete Rails project. This could be a detailed entry for the wiki, or be appended onto the README.

Add a flag to the init command to allow use to choose which version of Rails to use. That version should be reflected in the Dockerfile FROM instruction.

Right now, regardless of the base image chosen, there is no option to specify additional development dependency packages to be in installed. This means that if a gem has a special dependency, the installation will fail.

There should be some sort of --dependency flag to specify additional dependencies.

The tricky part is that each base image has its own package manager, etc. Needs some design thought on how to handle all of the different edge cases.

It would be nice to adopt a code guideline, rubocop is sorta good.

The README is a bit thin when it comes to development setup/testing instructions.

We need to include explicit instructions on how to:

• create a new branch
• reference the branch in the Gemfile
• view test coverage (has an rcov html file now)

This could be unexpected...

Maybe we should name the Dockerfile as Dockerfile.flatcar and then add dockerfile: Dockerfile.flatcar to the docker-compose.yml?

Hey folks, it looks like this org is unused, and only holds a fork from the CenturyLinkLabs/flatcar project, which is equally quiet (since 6 years).
I work on a very active Linux project called Flatcar (github.com/flatcar-linux) and it would help our community a lot to be able to have the simpler github URL.
Would you be open to retiring/renaming this org?
Not sure who the owner is, so I'm tagging the two main contributors @rheinwein @dharmamike

flatcar init -b default should be allowed. A new value needs to be added to init.rb. If the value passed is invalid, flatcar should fallback to the library Rails image.

Right now, flatcar init is used for both starting a brand new project, as well as creating a dockerized (flarcar-ized?) version of an existing Rails project.

Suggestion:
flatcar new should create a brand new Rails project (i.e. execute the rails new command)
flatcar init $path should dockerize an already existing project (i.e. create the docker-compose.yml and Dockerfiles).