The heroku page for Task Off is Taskoff.herokuapp.com - Please try it out. The concept did come from Bloc and not something I will be purusuing further, So feel free to fork it and have fun.
The code is on my Github and here is the Gist I started this from. I will be starting Block Marks tomorrow morning and excited to implement different concepts.
This is my personal blog and journey in learning a new skill, Web Developing. In only 7 months I made a career change into this field by dedicating 25(avg) hours a week in studying Ruby. #All words are my own, except the ones I copy and pasted.
Showing posts with label web app. Show all posts
Showing posts with label web app. Show all posts
Friday, January 24, 2014
3rd App complete: Checking logs for errors.
I am just about to finish my 3rd month learning programming and stoked that I have completed my 3rd web app. I spent about 20 hours building it and maybe another 5 this week cleaning it up. This was also my first app that I did not follow a tutorial to build, although I did reference some old tutorials for specific things and used a Rspec tutorial as a guideline.
I am looking forward to starting my 4th app Blockmarks, which involve quite a few things I have not implemented. More on that to come.
I do want to pass on some advice as well as remind myself to check the logs when debugging. I always start with the error on the localhost page but alway forget to check the "rails server" log for the root of the issue. I found a pattern when I kept getting stumped and going to my mentor for help, only to find out my answer was in the log.
This morning I had an error running my app on the Heroku. I wrote a long message with embedded code to my mentor and realized I did not even check the heroku log. I ended up deleting my message and will work on the solution some time today. I will share the app later once I get a chance to fix. For here is the Github
Remember to check your logs. cmd+f "error"

I am looking forward to starting my 4th app Blockmarks, which involve quite a few things I have not implemented. More on that to come.
I do want to pass on some advice as well as remind myself to check the logs when debugging. I always start with the error on the localhost page but alway forget to check the "rails server" log for the root of the issue. I found a pattern when I kept getting stumped and going to my mentor for help, only to find out my answer was in the log.
This morning I had an error running my app on the Heroku. I wrote a long message with embedded code to my mentor and realized I did not even check the heroku log. I ended up deleting my message and will work on the solution some time today. I will share the app later once I get a chance to fix. For here is the Github
Remember to check your logs. cmd+f "error"

Wednesday, December 11, 2013
First Rails App is Live and Ready To Go
I have finally figured out how to implement comments (sort of) on to my app, which was the reason for the delay in sharing with my friends. I later found out it was an error in my code, I am on Rails 4 and the code attr_accessor with my comment.rb does not work in 4.
I originally wanted to add native comments that live within the app, but I had a lot of trouble implementing them properly, so I just went with Disqus.
Disqus is great platform and actually very easy to implement the Javasrcipt. Just paste the code and you are good.
If you get a chance please check out my app and post a picture. bit.ly/robotapp1
I originally wanted to add native comments that live within the app, but I had a lot of trouble implementing them properly, so I just went with Disqus.
Disqus is great platform and actually very easy to implement the Javasrcipt. Just paste the code and you are good.
If you get a chance please check out my app and post a picture. bit.ly/robotapp1
Subscribe to:
Posts (Atom)