what is this? After cloning ServiceStack.Examples from GitHub down to my local drive, I thought the root of ServiceStack.Examples was all it, meaning that was all the examples but then we have this repeated "ServiceStack.Examples" folder within the root also, can someone explain what is going on here? It's not making any sense in terms of organization and what is what.
As mentioned in this previous answer, ServiceStack.Examples was the first public example demo created for ServiceStack. Many years ago it was the only example in the project, we then started adding different standalone demos and so ServiceStack.Examples got pushed into its own folder.
Now instead of creating more stand-alone demos in SS.Examples we instead prefer to develop small, use-case focused examples as seen in ServiceStack.UseCases.
Related
I am working on a project that has a few different code-bases (mostly Meteor), but they all use some of the same API code (schemas, publications and methods).
It doesn't seem very intuitive to have one repository and use sub-trees/sub-modules in my case. Maybe I'm wrong and somebody could help clear it up.
An example structure of my project:
project-landing-page (meteor app for collecting leads and offering basic account management)
project-app (an angular/ionic/cordova/meteor app that is distributed via the app store)
project-worker (a set of cron-like scripts that are executed in the background to manage the data in the mongo instance)
They all share the same schemas, and the two meteor apps use the same methods and publications. It seems a bit cluttered to have one repo for all of this code. Making a branch for the app would also branch the code for the worker scripts. That just seems messy.
Would it be okay to have another repo called "project-apis", that provides the shared code an could be cloned into the other projects? What are the drawbacks? Other than having to run git pull when the "project-apis" repo is updated, I can't really see any.
Would any git-wizards be able to chime in?
Thanks!
I have created a C++ application using Pjsip Stack and my next step to create a plug-in,for which i am using firebreath. Being a newbee, I dont have any idea of including my C++ project in Firebreath application. Although I searched many links for over a week and tried stuff on my own, I couldnt come up with solution to my problem.
If I can get any guidance for the same I'll be grateful.
The first step is to learn how to write a firebreath plugin, which you can do by going to http://firebreath.org and following the tutorials. You need to keep a few things in mind, though:
Plugins have a different lifecycle than applications.
They start when the browser says and have to go away when the browser says and they can't block the main thread.
They run in a process that they don't own.
Global variables are shared between all instances of the plugin
There could be any number of said instances
Things like the current working directory should probably be left alone.
Turning an application into a plugin is more a process of porting than it is of embedding, and how hard it is depends on how well the application is written; remember that your plugin could be instantiated and destroyed many times before the process is unloaded, so if you have memory leaks it can be a major problem.
The main thing, though, as I said earlier, is just to learn how to write a firebreath plugin. You can best start that by looking at the examples in the repo (particularly fbtestplugin) and following the tutorial to create a new project, then just play until you figure it out. There is an IRC chat room and a google group where you can get help.
I want to start a new project using tower.js, I did some research and I think it's very cool, but after I installed it and tried to generate a new project using tower new app I got this: Cookbook [app] not found. I know that tower changed the way the generators work and now are built from cookbooks, but I'm not really an expert on this kind of stuff, so I would like to get some recommendations about how to generate a new project?
Thanks in advance!
As mentioned in another answer, Github is the best place to resolve issues and ask questions. We're not on the IRC either.
We've been currently putting a lot of effort into the client-side of things. Thus, the cookbooks aren't finished (the same goes for the new cookbook). We'll be bringing those pieces to standard very soon.
I'm using markdown and reveal.js to create presentations, and want to start using node.js to serve them from my website.
I've read the docs for reveal.js and it seems like it's easy to do for one presentation, but trickier for several. For example, I'd like
http://mysite/presentations/rabbits
and
http://mysite/presentations/deer
to run on the same instance of node, but each point to a different presetation. Is this possible natively (or with existing plugins), or will I have to hack something together myself?
I know, just three years late. But in case anyone might end up here to look for an answer, there's a working recipe over here: https://web.archive.org/web/20151223044405/https://medium.com/#KienanKB/serving-multiple-reveal-js-presentations-b1a5c086e959 (archived link to the now removed article).
Note: Reveal.js changed the part defining what files it watches:
html: {
files: [ ‘index.html’ ]
}
Instead of ‘index.html’ it now reads ‘*.html’.
The recipe still works fine though.
As long as you're using basic features you don't need node.js at all - just drop the reveal.js distribution in every presentation folder where it is served statically.
Another option is hosting on github pages, I've checked it now for this scenario and it seems to be served right.
You might also want to raise this issue at the project page https://github.com/hakimel/reveal.js/issues
We started using the kohana project template from synapses studio :
https://github.com/synapsestudios/kohana-projecttemplate
It's great but the problem is that there is no real documentation for it and I haven't been able to find a good tutorial about it. Basically you need to read every modules' documentation to get an overview of it, quite a pain and complicated to accomplish.
I think what is missing here is a get-started tutorial....
Would someone know where to find info on how to start with it, like configuring the database and htaccesses etc, or maybe be able to write a simple tutorial on the first steps to get started?
Actually after some searching I found this :
https://github.com/patricksebastien/kohana-3.2-example
This approach is a little different than the synapses studio, but it's great anyway!
Simple, self-explanatory, and already implementing i18n and Authentication, installed in 2 minutes!