43c1dac627
This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener). # Fixed URLs ## Fixed But Review Recommended These URLs were fixed, but the https status was not OK. However, the https status was the same as the http request or http redirected to an https URL, so they were migrated. Your review is recommended. * http://m2.neo4j.org/releases (404) with 5 occurrences migrated to: https://m2.neo4j.org/releases ([https](https://m2.neo4j.org/releases) result 404). ## Fixed Success These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended. * http://maven.apache.org/xsd/maven-4.0.0.xsd with 11 occurrences migrated to: https://maven.apache.org/xsd/maven-4.0.0.xsd ([https](https://maven.apache.org/xsd/maven-4.0.0.xsd) result 200). * http://repository.jboss.org/maven2/ with 1 occurrences migrated to: https://repository.jboss.org/maven2/ ([https](https://repository.jboss.org/maven2/) result 200). * http://download.osgeo.org/webdav/geotools with 1 occurrences migrated to: https://download.osgeo.org/webdav/geotools ([https](https://download.osgeo.org/webdav/geotools) result 301). * http://m2.neo4j.org/content/repositories/releases with 1 occurrences migrated to: https://m2.neo4j.org/content/repositories/releases ([https](https://m2.neo4j.org/content/repositories/releases) result 301). * http://m2.neo4j.org/snapshots with 3 occurrences migrated to: https://m2.neo4j.org/snapshots ([https](https://m2.neo4j.org/snapshots) result 301). * http://maven.apache.org/maven-v4_0_0.xsd with 4 occurrences migrated to: https://maven.apache.org/maven-v4_0_0.xsd ([https](https://maven.apache.org/maven-v4_0_0.xsd) result 301). * http://www.neotechnology.com with 1 occurrences migrated to: https://www.neotechnology.com ([https](https://www.neotechnology.com) result 301). * http://www.spring.io with 3 occurrences migrated to: https://www.spring.io ([https](https://www.spring.io) result 301). * http://www.springsource.org/spring-data/neo4j with 1 occurrences migrated to: https://www.springsource.org/spring-data/neo4j ([https](https://www.springsource.org/spring-data/neo4j) result 301). * http://maven.springframework.org/milestone with 8 occurrences migrated to: https://maven.springframework.org/milestone ([https](https://maven.springframework.org/milestone) result 302). * http://maven.springframework.org/release with 10 occurrences migrated to: https://maven.springframework.org/release ([https](https://maven.springframework.org/release) result 302). * http://maven.springframework.org/snapshot with 3 occurrences migrated to: https://maven.springframework.org/snapshot ([https](https://maven.springframework.org/snapshot) result 302). * http://repo.spring.io/plugins-release with 1 occurrences migrated to: https://repo.spring.io/plugins-release ([https](https://repo.spring.io/plugins-release) result 302). * http://repository.ow2.org/nexus/content/repositories/ow2-legacy with 1 occurrences migrated to: https://repository.ow2.org/nexus/content/repositories/ow2-legacy ([https](https://repository.ow2.org/nexus/content/repositories/ow2-legacy) result 302). # Ignored These URLs were intentionally ignored. * http://maven.apache.org/POM/4.0.0 with 30 occurrences * http://www.w3.org/2001/XMLSchema-instance with 15 occurrences Original pull request: #463
Spring Data Neo4j Todos
A simple todo list using Spring Data Neo4j, configured for easy deployment to Heroku.
Get Ready
To prepare for deploying to Heroku, you must first become a Hero:
- Create an account on Heroku
- Install the
herokucommand-line client - See the Heroku Quickstart for details
Feel ready? OK, then get a copy of this project and checkout the heroku-deploy branch:
git clone git://github.com/SpringSource/spring-data-neo4j.git
cp -r spring-data-neo4j/spring-data-neo4j-examples/todos .
cd todos
Local build and run
- Run a local Neo4j server (using default config)
export NEO4J_REST_URL=http://localhost:7474/db/data
export NEO4J_LOGIN=""
export NEO4J_PASSWORD=""
- Build, then run locally
mvn package
sh target/bin/webapp
- check that it is working (in another terminal, but same project directory)
./bin/todo mk "tweet high praises to @neo4j"
./bin/todo list
Satisfied? Then ctrl-c to kill the application.
Deploy on Heroku
Initialize a local git repository:
git init .
git add .
git commit -m "the start of my own todo application"
Create a new provisioning stack on Heroku for the app. Heroku will notice that you've got a git repository, adding itself as a remote.
heroku create --stack cedar`
heroku addons:add neo4j
git push heroku master
Check to make sure it is running with heroku ps, which should show a web.1 process with an "up" state.
Finally try it out using the -r flag to indicate remote access.
./bin/todo -r mk "tweet thanks for the good work @mesirii @akollegger"
./bin/todo -r list
To see the Neo4j graph you just created through Heroku, use heroku config to reveal the NEO4J_URL
which can take you to Neo4j's Webadmin. Have fun!
For details about preparing your own Spring Data Neo4j application for deployment to Heroku, see the Heroku chapter in "Good Relationships: The Spring Data Neo4j Guide Book".
Don't forget to decommission the Heroku application when you're done with it.
Use heroku destroy to free up the instance.
CLI Tool
A simplistic todo script in the bin directory can directly create, delete and list todos.
Usage: todo [-r] [ list | mk | rm ]
todo -r - access the remote (Heroku) todo application
todo list - list current todos
todo mk "a new todo" - to create a todo
todo rm 1 - to remove the todo with id 1