1) makes sign in button larger
2) changes "Current Shop" menu text to "Sign In" for normal user
3) takes all users after submitting contact to Sign In page rather than only new users.
Originally, deposits of $0 (amount > 0) would not be considered real deposits, however, there may be shops where only non-monetary transactions occurred (amount >= 0) which would be useful to record in an accounting program.
One caveat, if a monetary transaction is recorded, but the depositor only enters $0, the deposit will show "Difference: n/a", however this should be a cue since it should be obvious that a real world deposit of $0 would not be made at a bank.
1) Not necessary for a production site
2) Great for testing from the interface when a shop needs to be deleted, however, this can be done just as easily directly through the database.
1) Bots like to follow the delete link on demostrations and delete all the time-in entries.
2) YBDB adhers to open trust metrics that are common at bicycle collectives, bots really do not care about trust including bots from google, they love exploring every link though.
3) This functionality isn't really necessary since it is possible to make the sign-in time the same as the sign-out time if the person changes their mind about their visit.
1) updated information on how to ensure that passwords are hidden even wehn KeePass is opened.
2) added docker.txt which goes into details about sysadm of docker.
There are other things that can be done within the terminal to prevent tampering, e.g., read-only environment,
but the above protects the password from hacking, eavesdropping, and from regular users
in the shop, basically, only the sysadmin and bookkeeper should have remote access via the password.
So, YBDB, although on the internet will be confined to the terminal(s) you allow it to be on, and
the Point of Sale will be at the proper location .. at the front of the Community Bike Shop where people
walk-in/walk-out.
1). In confs, update works well, delete has an issue with on delete cascade.
2). Saves state properly. Now just need to create a front-end to query for volunteer organizers.
1). Directions are in database_functions.
2). Initial population occurs on first submit.
3). Interests can be changed or deleted
4). It isn't a GUI interface, but it is useful for those without a MySQL understanding.
1) Pages will go back to shop_welcome (original behavior) but for these two pages. This prevents transaction pages from going back.
2) Added an About/Help link to the left.
3) Changed the width/margin of the associated tables so that it would line up withe new table presenting the menu links.
also ..
1). zip to Zip Code .. some day will need to make international
2) changed Fill-in Form to "Check them out!" for volunteer interest .. subject to real world testing.
- mailman specific
- has been tested to work properly for both subscribe, and unsubscribe
- uses node.js
- two stage security
1) password is specific to connector for recognization
2) password used by list not kept local
- ssl used for all communication
- yeah!
Define a url for an email connector that will connect to an email list.
The url can be a server:port, program, etc.
Name (First, Last) email address, and connector password will be sent to the connector.
The purpose of email connectors is to provide autonomy in the choice
of email services and programs. E.g. mailman, googlegroups
See ./examples for an example connector
1). Adds configuration options to turn off waiver & email_list options
2). Puts waiver in Connections/waiver.txt
3). New MySQL waiver column added, receive_newsletter used for email_list.
Jonathan Rosenbaum