dphaener / kanji Goto Github PK

When running kanji new with a dasherized name there are several locations that don't handle this properly in the templates.

e.g. Rakefile

task :setup do
  Foo-bar::Container.start :rom
end

should be:

task :setup do
  FooBar::Container.start :rom
end

Shotgun was a great initial choice for automatic code reloading, but it loads the entire app on every request. This is really not ideal. We should explore some different options.

I'd also like to fix the way that we are running kanji server. It currently just executes a shell command, which is less than ideal. I'd like to move it into it's own class so we can tie in the logging when running the server so that the user doesn't have to have a separate log tail going to see the logs. Also need to add the option to run on a different port, and tell the user which port the app is running on.

Possibly due to an API change, the settings container cannot be resolved automatically in the monitor setup. We have to use container.resolve(:settings) to grab it. This was not the case before. We should look into updating this in one way or another.

I am not sure if this was intentional or not, but this is writing to a file in the root directory called stdout. The way it's named I imagine this was unintentional?

The kanji s command does not currently detect if we are in a production environment and runs the server inside of the rerun context, which is not appropriate in production.