A talk given at MelbJVM November 2015 about producing our nametags using Docmosis Cloud.
Story here WHY_NAMETAGS.md
How you supply these too your application is up to you, you could :
- Put these in src/main/resources/application.properties
- Supply an application properties next to the war
- Put them in as environment variables
Here's what you want :
meetup_api.key=See above
docmosis_api.key=See above
security.username=a username of your choice
security.password=a password of your choice
- Avery white address labels, 14 per page. For software code L7163 / reorder code 959089.
-- Feel free to change
template5.docxreferenced insrc/main/java/io/github/linead/nametags/Docmosis.javato a different file of your own template choosing.
- The app is built on Spring Boot
- Maven
- Java 8
- Update keys in application properties as described in Requirements
- Upload template to Docmosis Cloud. See My Templates tab.
Use nametemplate5.docxor change code in the following step. - Update
template5.docxreferenced insrc/main/java/io/github/linead/nametags/Docmosis.javato a different file of your own template choosing to match what you uploaded. - Run it in one of 3 easy ways!
- run the executable war with java -jar
- stick the war in tomcat
- run it from maven with mvn spring-boot:run
Comment out the scope PROVIDED line for the org.springframework.boot:spring-boot-starter-tomcat dependency to pull in
the servlet jars normally provided by your container when building a war.
Lists upcoming MelbJVM events and event IDs required for following endpoints
Returns a list of attendees who have RSVPd YES to the meetup
Generates the pdf using the template
Check out the Template Guide and the API guide in Docmosis Cloud documentaion If you just want to get up to speed with the templating language quickly also checkout [https://www.docmosis.com/how-it-works/creating-templates.html]
Any questions contact Paul Jowett