Closed emilos closed 4 years ago
@emilos could you try huncwot server
or hc server
? The start
command is deprecated as I'm working on a tight integration with VS Code. Do you happen to use this editor ?
with hc server
you should get a following screen if there is no PostgreSQL instance running
I've decided to exclusively focus on PostgreSQL to force people to learn about certain beautiful features of that database that are usually hidden by an ORM. ;)
I'll update the documentation in a moment. I should've done it long ago.
Thanks, that's more helpful, I get the following error message here:
emilos@Emils-MacBook-Pro my-app % huncwot server
/Users/emilos/.nvm/versions/node/v12.14.1/lib/node_modules/huncwot/node_modules/config/lib/config.js:794
throw new Error("Cannot parse config file: '" + fullFilename + "': " + e3);
^
Error: Cannot parse config file: '/Users/emilos/Desktop/Projects/emilos/my-app/config/default.yml': TypeError: VisionmediaYaml.eval is not a function
at Config.util.parseFile (/Users/emilos/.nvm/versions/node/v12.14.1/lib/node_modules/huncwot/node_modules/config/lib/config.js:794:11)
at /Users/emilos/.nvm/versions/node/v12.14.1/lib/node_modules/huncwot/node_modules/config/lib/config.js:601:26
at Array.forEach (<anonymous>)
at Config.util.loadFileConfigs (/Users/emilos/.nvm/versions/node/v12.14.1/lib/node_modules/huncwot/node_modules/config/lib/config.js:600:16)
at new Config (/Users/emilos/.nvm/versions/node/v12.14.1/lib/node_modules/huncwot/node_modules/config/lib/config.js:116:27)
at Object.<anonymous> (/Users/emilos/.nvm/versions/node/v12.14.1/lib/node_modules/huncwot/node_modules/config/lib/config.js:1441:31)
at Module._compile (internal/modules/cjs/loader.js:955:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:991:10)
at Module.load (internal/modules/cjs/loader.js:811:32)
at Function.Module._load (internal/modules/cjs/loader.js:723:14)
The yaml file seems to be valid though (I've double checked in a yaml validator).
db:
database: "my_app"
username: "emilos"
deploy:
server:
src: .
dest: "YOUR DESTINATION"
delete: true
exclude:
- dist
- node_modules
- .git
- static/upload
- config/default.yaml
client:
src: dist/
dest: "YOUR DESTINATION"
delete: true
Any ideas?
@emilos Would it be possible if you (temporarily) install js-yaml
globally? Just to see if it solves the issue
npm i -g js-yaml
@zaiste bingo, thanks!
Maybe it makes sense to simplify this and just have a json
or js
file that does the same? I do understand the desire to use the lovely yaml syntax, but maybe it does not sense to have it out of the box? Less deps, less things to worry about etc.
I do use it in the engine too, considering to move it to a separate package though... not sure what's the best approach :)
I relate to this sentiment, but I would it keep it as-is for now and decide about it later. In the future we could just have a visual panel in VS Code and simply use json
underneath.
Does the lib require anything related to postgres to be set up, like a config file? (similar to rails)