I haven't been able to contribute to Cozy Notes very regularly, and every time I take a break from working on Notes, I forget the exact process for building. The README and our discussion on the forums use different commands for starting everything. So right now I want to help update the "Contributing" section of the README.
I notice that for Cozy Data System, the Cozy Notes server, and the Cozy Notes client, you can start all three with the command npm start. This might be a better way of telling users / develoeprs to do it, because it's much easier to remember that one command. The only problem is when you use npm start inside cozy-notes/client, you get this message:
info: application started on http://localhost:3333/
Which is strange, because if you go to that URL, the cozy notes app won't work. The Notes app is empty, and you can't create any new notes. You have to go to the server URL, at localhost:9201. So why does the client listen on a separate port, when it seems to be useless?
For everything else, npm start seems to work just fine, unless I'm missing something.
I haven't been able to contribute to Cozy Notes very regularly, and every time I take a break from working on Notes, I forget the exact process for building. The README and our discussion on the forums use different commands for starting everything. So right now I want to help update the "Contributing" section of the README.
I notice that for Cozy Data System, the Cozy Notes server, and the Cozy Notes client, you can start all three with the command
npm start
. This might be a better way of telling users / develoeprs to do it, because it's much easier to remember that one command. The only problem is when you usenpm start
insidecozy-notes/client
, you get this message:Which is strange, because if you go to that URL, the cozy notes app won't work. The Notes app is empty, and you can't create any new notes. You have to go to the server URL, at
localhost:9201
. So why does the client listen on a separate port, when it seems to be useless?For everything else,
npm start
seems to work just fine, unless I'm missing something.