3 ms·

It sounds like you were installing from source. There are indeed a lot of moving parts to deal with there. We also have a binary installer (and auto-updater) wh

by kentonv 12y ago

It sounds like you were installing from source. There are indeed a lot of moving parts to deal with there. We also have a binary installer (and auto-updater) which "just works" with essentially no dependencies. I understand some people aren't comfortable with binary installers, but you have to understand that building from source will always be more work. :) That said, feel free to file issues for any obstacles you encounter that aren't already covered in the docs. We do plan to stick with Meteor. It's a pretty awesome framework. I find Meteor is incredibly easy to get running, but this is again due to its binary installer script which maybe you don't like. :) I believe that Meteorite (the "mrt" tool which you had to install separately using npm) is slated to go away before Meteor 1.0 as that functionality will be rolled into Meteor itself. So, that part will get better, at least. For now, you actually can (and arguably should) install it using Meteor's bundled npm rather than the system npm.

e12e 12y ago
Actually, the mrt tool wasn't a problem (I had node installed from source, in my home-dir under opt from before -- working quite well with xstow. Meteor not installing from source is partly due to me running Debian stable -- I'm not surprised when bleeding edge frameworks won't compile, just a little bit disappointed ;). I was indeed installing from source, as that is a requisite for contributing to the project (if I can't build it how could I possibly submit patches). I have no problem with you citing any one distribution/version as supported however -- it would be madness to demand support for "everything" from an alpha source release! And I think aiming for cross-platform-distribution comparability would be wasted effort at this point. With Vagrant from wheezy-backports, everything came up fine -- just had to(?) increase the vms ram to 512 mb for ipython notebook to work. Now my only problem is figuring out how to get the hacker cms to publish anything (to users without login). I've understood that the cms should be stuffing files under /var/www (in my vagrant/virtualbox vm) -- so I'll have to check if "publish" pushes anything there -- and if there appear to be an nginx-instance set up to serve files from /var/www...). As for meteor -- I have a few reservation of their architecture in general -- but my main problem is the complexity of the setup -- especially how hart it seems to be to build everything needed from source. But then again, they're not yet at 1.0, are they? (Still seeing as how easy nodejs is to build from source, it is a shame meteor manage to somehow mangle that process...)
- kentonv 12y ago
  The recommended way to "publish" from Hacker CMS is to follow the in-app "DNS setup" instructions, rather than point nginx directly at the storage. The latter was the old way of doing it -- is there a doc you're seeing somewhere that still recommends that?
  - e12e 12y ago
    No, (not other than the api docs for devs, that explains that one way to publish from (any) app is to push files to /var/www). I guessed the dns-setup was one way -- wasn't sure if that would work without a routable address though (eg: 10.0.0.0/x on a lan). Or in my case, with the test setup in a vagrant box. [edit: That is, I couldn't find any docs on how to publish from hacker cms, but I did find this for devs: https://github.com/sandstorm-io/sandstorm/wiki/Publishing-to-the-user's-domain https://github.com/sandstorm-io/sandstorm/wiki/Publishing-to... ]
    - kentonv 12y ago
      If you click on the "Setup DNS" button inside the Hacker CMS app, it gives you instructions for how to publish to your domain.

by kentonv 12y ago

e12e 12y ago

Actually, the mrt tool wasn't a problem (I had node installed from source, in my home-dir under opt from before -- working quite well with xstow. Meteor not installing from source is partly due to me running Debian stable -- I'm not surprised when bleeding edge frameworks won't compile, just a little bit disappointed ;). I was indeed installing from source, as that is a requisite for contributing to the project (if I can't build it how could I possibly submit patches). I have no problem with you citing any one distribution/version as supported however -- it would be madness to demand support for "everything" from an alpha source release! And I think aiming for cross-platform-distribution comparability would be wasted effort at this point. With Vagrant from wheezy-backports, everything came up fine -- just had to(?) increase the vms ram to 512 mb for ipython notebook to work. Now my only problem is figuring out how to get the hacker cms to publish anything (to users without login). I've understood that the cms should be stuffing files under /var/www (in my vagrant/virtualbox vm) -- so I'll have to check if "publish" pushes anything there -- and if there appear to be an nginx-instance set up to serve files from /var/www...). As for meteor -- I have a few reservation of their architecture in general -- but my main problem is the complexity of the setup -- especially how hart it seems to be to build everything needed from source. But then again, they're not yet at 1.0, are they? (Still seeing as how easy nodejs is to build from source, it is a shame meteor manage to somehow mangle that process...)

kentonv 12y ago
The recommended way to "publish" from Hacker CMS is to follow the in-app "DNS setup" instructions, rather than point nginx directly at the storage. The latter was the old way of doing it -- is there a doc you're seeing somewhere that still recommends that?
- e12e 12y ago
  No, (not other than the api docs for devs, that explains that one way to publish from (any) app is to push files to /var/www). I guessed the dns-setup was one way -- wasn't sure if that would work without a routable address though (eg: 10.0.0.0/x on a lan). Or in my case, with the test setup in a vagrant box. [edit: That is, I couldn't find any docs on how to publish from hacker cms, but I did find this for devs: https://github.com/sandstorm-io/sandstorm/wiki/Publishing-to-the-user's-domain https://github.com/sandstorm-io/sandstorm/wiki/Publishing-to... ]
  - kentonv 12y ago
    If you click on the "Setup DNS" button inside the Hacker CMS app, it gives you instructions for how to publish to your domain.