Skip to main content

Using a separate settings file with Abbot and Sproutcore 1.6

In some cases it is practical in an application to have a single global settings file where all configuration is stored. Most often this configuration file varies between a deployment and another, depending on customer requirements, licensed features, backend technology, etc.

When developing an application with Sproutcore 1.x (1.6 is assumed) it is not immediately clear how to do it, not because it is not possible but just because documentation on Abbot, SC's build tool is, to use an euphemism, well, scarce.

So what do we want to do exactly? We want to have a single config.js file that is included before any other application file and, most importantly, must not be minified and packed so that on-the-fly editing or inspection is still conveniently possible. The file should be kept small anyway so that packing and minifying it is not going to be necessary.

To do this we need to create a new .js file and place it wherever we like in the application tree. A sensible choice would be to have a config directory, but it's really up to you. I'm a lazy bloke so I will create this file in the application root where the theme.js, main.js and core.js reside. Let's call this file appconfig.js.
We can put any content we wish inside, but the really important thing to do is to insert this directive near the top:

sc_resource('appconfig.js')

This directive which is mentioned in passing here (third item in the section Other Notable Changes) instructs Abbot to put the content of this file in a separate resource called, you guessed it,  appconfig, instead of the global javascript.js resource.

In the next step we will tell Abbot to add this file straight before our application code so that it is picked up correcly. To do that we use an another directive, which has to be added to the Buildfile.
Open up your app's Buildfile in The Editor (vi, that is) and add a bootstrap directive like the following at the end of config:

config :all, :required => [:sproutcore, 'animation', 'sctable', :'sproutcore/experimental/split_view'], :minify => true, :bootstrap => 'appconfig'


Now delete the tmp directory (not really required, but it helps) and restart sc-server. Refresh the page in your browser and inspect the html source: you should find a javascript include of your app's config file almost at the top of the include chain. Rebuild your app in production mode and notice how the config file is kept separate from all others, just as we wish.
Boostrap's brothers Boostrap-inline was mentioned by Tom Dale in this conversation and it is where I got the inspiration to look for bootstrap from. You may want to use bootstrap-inline to have the javascript code embedded directly in the html. If you choose to use bootstrap-inline remember to also add SC's own inlines or it will stop working.

Comments

Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

RUNDECK job maintenance

Learn more about Rundeck.

Now that I have a fair number of jobs scheduled by Rundeck, how do I periodically prune the job execution history and keep only the last, say, 30 executions for each job?