✏️ Free Opensource Alternative to TypeForm or Google Forms
Go to file
2016-04-22 19:39:11 -04:00
app readded ui-select 2016-04-22 19:39:11 -04:00
config added env.PORT back for production environment 2016-04-21 16:35:00 -04:00
docs fixed merge conflicts 2015-11-16 14:25:39 -08:00
public readded ui-select 2016-04-22 19:39:11 -04:00
scripts fixed merge conflicts in app/models and app/tests 2015-10-06 13:24:02 -07:00
.bowerrc added automatic bower dependency injection 2015-07-03 12:25:02 -07:00
.csslintrc first commit 2015-06-29 15:51:29 -07:00
.editorconfig first commit 2015-06-29 15:51:29 -07:00
.gitignore added ecosystem.json to gitignore 2016-04-21 16:22:06 -04:00
.jshintrc got css and js files to pass linting 2016-04-16 22:45:17 -04:00
.slugignore first commit 2015-06-29 15:51:29 -07:00
.travis.yml Fixed tabbing validation error in travis.yml 2016-04-21 11:02:32 -07:00
app.json Update app.json 2015-11-21 12:59:03 -08:00
bower.json added angular busy back to bower 2016-04-21 16:53:03 -04:00
conf.json added jasmine-core 2015-12-12 12:13:43 -08:00
docker-compose.override.yml.template Create docker-compose.override.yml.template 2016-04-21 12:16:52 -07:00
docker-compose.yml Create docker-compose.yml 2016-04-21 12:16:19 -07:00
Dockerfile Fixed dockerfile 2016-04-21 12:17:45 -07:00
ecosystem.json update ecosystem.json with polydaic user 2016-04-20 11:21:55 -04:00
gruntfile.js fixed travis setup for karma 2016-04-21 14:59:42 -04:00
karma.conf.js added jasmine-core 2015-12-12 12:13:43 -08:00
LICENSE.md first commit 2015-06-29 15:51:29 -07:00
package.json Update package.json 2016-04-21 13:17:53 -07:00
Procfile first commit 2015-06-29 15:51:29 -07:00
protractor.conf.js added testing 2015-08-18 14:44:36 -07:00
README.md Update README.md 2016-04-22 15:55:53 -07:00
server.js added node-coveralls to package.json 2015-11-23 13:06:02 -08:00

TellForm

Current stable release: v1.2.1

Build Status Dependency Status Code Climate

TellForm is an opensource alternative to TypeForm built ontop of nodejs that can create stunning forms from PDFs or from scratch

##Demo Forms Job Application Example

Features

###Currently following features are implemented: -User login system to manage forms -User CRUD -Form CRUD -11 possible types of form fields -Editable startpage -Push form data to OsacrHost EMR -Create forms from FDF-formatted PDFs (unstable) -Save form submissions as FDF-formatted PDFs (unstable) -Toggle forms as private (viewable only if logged in as Form's user) or public (viewable by anyone) -Drag and drop functionality to editing form field order -Editable form submissions (half-done)

###TODO: -Implement encryption for all form data -Integrate AWS for PDF saving -Add Typeform API integration -Add plugin/3rd party integration support (ala Slack) -Create wiki for easy installation and setup -Create mockups for different user view designs

Quickstart

Install dependencies first.

$ npm install
$ bower install

Setup environment.

$ grunt build

Create your .env file. It should look like this

MAILER_EMAIL_ID=example@test.com
MAILER_FROM=noreply@yourdomain.com
MAILER_PASSWORD=yourmandrillapikey
MAILER_SERVICE_PROVIDER=Mandrill
BASE_URL=yourdomain.com

Create this directory or you will get errors.

mkdir uploads/pdfs

Edit the 'env' config in gruntfile.js to make sure your .env file is being used. If you don't include this your app won't run

To run development version:

$ grunt default To run production version:

$ grunt production

Your application should run on port 3000, so in your browser just go to http://localhost:3000

Testing Your Application

You can run the full test suite included with MEAN.JS with the test task:

$ grunt test

This will run both the server-side tests (located in the app/tests/ directory) and the client-side tests (located in the public/modules/*/tests/).

To execute only the server tests, run the test:server task:

$ grunt test:server

And to run only the client tests, run the test:client task:

$ grunt test:client

Currently the live example uses heroku github deployments. The Docker file is out of date and does not work. If someone wishes to get it working feel free to submit a pull request.

To calculate your total test coverage with Istanbul, run the coverage task

$ grunt coverage

To calculate your server-side test coverage with Istanbul, run the coverage task

$ grunt coverage:server

To calculate your client-side test coverage with Istanbul, run the coverage task

$ grunt coverage:client

Running in a secure environment

To run your application in a secure manner you'll need to use OpenSSL and generate a set of self-signed certificates. Unix-based users can use the following command:

$ sh ./scripts/generate-ssl-certs.sh

Windows users can follow instructions found here. After you've generated the key and certificate, place them in the config/sslcerts folder.

Credits

Inspired/built off the great work of the MeanJS team.