This Enova hosted meetup was an intense session of assembling the pieces of IFTTT.com, Twitter apps, and Etsy. We also created a fake WordPress application using Sinatra which forwarded an IFTTT request to our own Twitter application. Details and instructions -> http://meetu.ps/2wFpg2
The result: each time I favorite an Etsy item, IFTTT sends a message to my fake WordPress site, which sends a call to my Twitter app and tweets the item’s picture.
I met some nice friends which made it a great night!
Own Your Expertise by < write/speak/code > was a brilliant event full of truly effective exercises.
The first exercise was to state a self-deprecating thought that is holding you back. One person said she never tells anyone she graduated from MIT because they might expect too much of her. It seems women, myself included, avoid anything that sounds like bragging.
Another exercise was to state our expertise and back it up with 3 supporting points. My new expertise is on Michelle Waldorf.
Lastly, Coraline had us choose an open source project on Github. I’m looking at Bundler or Exercism.
I’m looking forward to working with all my new friends!
I created a nice little user page on GitHub in a few minutes. dietpop.github.io or www.michellewaldorf.com
I always like to monkey around with the colors and images on a standard template. The images are contained as version controlled files in Github because I used Github’s automatic page generator. Github won’t let me overwrite the image files so they have to be hosted outside of the project files.
One solution is to put the new image on another server that you have handy, but a better solution is to use Github’s issue tracking system to host the image.
Here’s the workaround:
- Create a new issue within your GitHub project page. Attach your new image to the issue. Hit the “Submit new issue” button.
- Edit the issue you just created to see the url of the image rather than the image itself. Copy the Github url for the image location. It should look like this – https://cloud.githubusercontent.com/assets/3495428/5651152/a6dbfd66-966a-11e4-84cd-589feb7ae9a2.png
- Change your user page html or css to use this non-version controlled image URL. Example – change “url(../images/download-sprite.png)” to “url(https://cloud.githubusercontent.com/assets/3495428/5651152/a6dbfd66-966a-11e4-84cd-589feb7ae9a2.png)”
My big change? Added the OctoCat.
I’m using Nitrous.io to host the work-in-progress RoR version of my old PHP 4 site, www.esellerstreet.com. Nitrous.io should work until the site is production quality and people start using it. Then I’ll switch to the heroku.com cloud platform for deployment.
The paid version is $19.99 per mo and lets me use my domain name and keeps the server running. The free version of Nitrous.io stops your server when you close your browser window which ends the session.
You have to use tmux to keep the server session alive in the background. “TMUX is a terminal multiplexer. It lets you switch easily between several programs in one terminal, detach them (they keep running in the background) and reattach them to a different terminal.”
Nitrous.io’s documentation is too sparse for me, so here is exactly what I did to keep my site alive after closing the nitrous.io web IDE.
- From the Nitrous.io dashboard, open the web IDE for the project.
- In the console at the bottom of the IDE enter tmux new -s my_session at your top level directory.
- Next change the directory to your project -> type cd ess (ess is my project directory)
- Start the server by typing Rails Server
- Preview your site in another browser tab or window to make sure it’s running.
- Close the nitrous.io IDE browser tab/window. Check that your site is still running.
Let me know if this doesn’t work for you or if you have suggestions. My contact info is here.
Nitrous.io help page for tmux
A day in the life of a SW Developer – Girl Develop It