You shouldn’t need to run 'npm install' inside the module folder unless the author specifically told you to do that.

So just looking at this, and all you amazing folks who are eager to jump in and start writing code … seriously, you all should. That’s no joke … start somewhere. There’s plenty of information on the web, and several folks here who can also help.

Anyway, my take on this:
Doing a local folder with pictures, while possible, also adds a lot of unknowns. For example, the images might not necessarily all be the same physical dimension, and loading one might go really fast while loading another will be rather slow because it’s so much bigger and you’re scaling it down. Or, or you pre-process your images to a specific size and then upload them to the rpi. BUT! Why do that when there are services out there that automatically do that for you? Let’s look at options:

Flickr has a public API: https://www.flickr.com/services/api/
They even have a node.js API kit making it easier to integrate: https://www.npmjs.com/package/flickrapi

iCloud API … iCloud API … anyone, iCloud API? (sorry, Ferris Bueller reference there.)
Same goes for Facebook …
And unfortunately, also Google Photos. They terminated development on the Picasa API on May 1st, but have yet to open their Photos API to the public. So you’re stuck using the Picasa one for now till they completely shut it down, at which point you can only hope they would’ve released the new one.

Exactly, that’s an external, server-side process.

JavaScript can’t do that. You need a server-side process to do that for you. But if the token doesn’t (ever) change, you can hard code it in the JS and not have to write it to disk anywhere.

Theeeeen you’re not defining it as a function … ?

I suspect the answer is: go read the source code … but, what are you trying to do?

I’m glad that has helped you. It doesn’t matter what kind of setup one uses, it’s unique for everyone. So if what you’re doing is working for you, even better. I try not to tell anyone whether something’s better done a different way, I would rather make recommendations and let folks decide for themselves what’s best for them.

Essentially you are using your own github account to do that. Write your code, commit it to github, and then share it with the rest of the world. Github has extensive help pages on their site. A good beginner’s guide is here: http://product.hubspot.com/blog/git-and-github-tutorial-for-beginners

I would recommend you start there and when you get stuck (or if you get stuck), let us know where/how, and we can try to help resolve the issue then.

For me the whole thing is integration. How to get devices integrated into the current ecology without needing additional ‘anything’ to be added. So I didn’t have to install npm nor electron on my work station, I already had all the necessary tools. And why work on separate copies of the software in different locations, that causes confusion later. I keep it all in one location, and use it from there.

And with the addition of Git, even if I horribly break something, I can always revert the code to an earlier state simply by going to Git and checking out an earlier commit state. Instant backup and revision control.

My setup at the office is similar, except instead of the rpi, I have it running as a serveronly on one of my large servers (replace the Raspberry Pi for a server in the layout above). But that’s really the only difference. Everything else is the same.

@monsieurpouet said in Module with Toshl API:

(not me, I’m a really really bad developer)

At some point, we were all bad developers. You have to start somewhere. Don’t be scared about it, just dive in. There are plenty of resources online that can help you, and there are several folks on here who can also give you a hand. Don’t underestimate yourself.