Small tweaks to make

[dbashford]

1. In the mimosa-config, serverReload.watch, change the array to apply to just your file. I have all those in there to cover all the possible bases that mimosa new delivers, but you obviously only have the one server file. You also don't have a routes a src and a lib.
2. serverReload again, for exclude and validate you have the defaults, so you can remove those and just leave the 1 entry watch array.
3. Remove all the comments from the mimosa-config and just leave the active config. There isn't much active config, and thats one of the points of mimosa. You get a lot for a little. I leave the rest of the commented config in there in case people find it useful when they are first getting started, but theoretically a skeleton is supposed to bypass the "getting started from scratch" step.
4. Run mimosa config to generate the fully commented config file and check that in along side the drastically reduced mimosa-config.
5. Remove bower.json and the bower module if you are not going to use them. It's ok to not use them, just no need to keep them around confusing the project.

That's all I've got from a Mimosa perspective. Otherwise I'd just encourage adding a little bit of dynamic behavior, just a little. It's a skeleton, you don't want to write too much code that people are just going to delete before getting started with their own stuff, but its good to just show a little bit of wiring together of some complex functionality.

[Anachron]

Thanks for the feedback!

1-3.) Pretty self explaining, will do it in short term.

4.) I don't quite understand. Mimosa config will store the default configuration file in my project, or am I wrong? Last time I did it at least. In step 3 you told me to remove all not required options.

5.) Thanks, I didn't see it. I planned to use it but I didn't dig into it yet. I will remove it.

About the little advanced stuff:
That's what issue #4 is for. I will write some basic code to start EmberJS-based apps, small ones like mini-module for contact (maybe signup) and bigger ones for Reading data from local filesystem (maybe mimosa) and push them out with custom helpers (issue #2).

Will update this again whenever there is progress.

[dbashford]

mimosa config creates a mimosa-config-commented.coffee so you have the best of both worlds. A slim and tiny actual config with a useful guide to that config alongside it.

[dbashford]

mimosa config will ALSO create a mimosa-config.coffee, but only if you don't already have one.

[Anachron]

Okay, awesome, another thing I have learned.
I totally missed that out. I guess I should read the mimosa.io pages again =)

[Anachron]

If you still have any more points, make sure to let me know. Else I will push a PR for this skeleton.

[dbashford]

You can remove the wrapping brackets in the mimosa-config, other than that and a bit more code you are good. But you don't need more code to justify making this a skeleton.

[Anachron]

More code to follow, there will be an example of using the new EmberJS Beta.
I will fix the wrapping brackets and push a PR.

[Anachron]

@dbashford that's everything you asked for, right? If you still look for more code, I will implement a simple ToDo list in the next days.

[dbashford]

I've been traveling for work and haven't done anything mimosa related for a few days.

Back at it today though. I'll get this merged in.

---

On 2013-11-07 12:10:16 +0000 Anachron [email protected] wrote:

@dbashford that's everything you asked for, right? If you still look for more
code, I will implement a sime ToDo list in the next days.

---

Reply to this email directly or view it on GitHub:
#6 (comment)

[Anachron]

Alright, finally. Don't let work cut off your open source productivity :-)