Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Releases: deck9/input

v2.0.1 Team Invitions Fix

13 Sep 15:29
@PhilReinking PhilReinking
b3d108c
This commit was signed with the committer’s verified signature.
PhilReinking Philipp Reinking
GPG key ID: 74AD07B86C02AAE9
Verified
Learn about vigilant mode.

Choose a tag to compare

This fixes a bug where email invitations could not be sent anymore

Full Changelog: v2.0.0...v2.0.1

Assets 2
Loading

v2.0.0 Docker Improvements

13 Sep 07:32
@PhilReinking PhilReinking
6c04e82
This commit was signed with the committer’s verified signature.
PhilReinking Philipp Reinking
GPG key ID: 76B4E27EA187C9B3
Verified
Learn about vigilant mode.

Choose a tag to compare

What's Changed

Migrating from Input v1.x to v2.x

Caution

This release introduces breaking changes. New images no longer come with a pre-generated APP_KEY. You must retrieve your current APP_KEY and set it manually to continue using Input.

Step 1: Retrieve Your Current App Key

Before upgrading to v2.x, retrieve your app key from your current installation:

# Replace "input" with your container name if different
docker exec input sh -c 'if [ -f ".env" ]; then cat ".env" | grep APP_KEY; fi'

Save this output for later use.

Step 2: Generate a New App Key

Generate a new APP_KEY using:

echo -n 'base64:'; openssl rand -base64 32

Keep this new key separate from the one retrieved in Step 1.

Step 3: Update Your Configuration

If Not Using docker-compose:

Create or update a .env file in your project root:

APP_URL=<YOUR_APP_URL>
APP_KEY=<YOUR_NEW_APP_KEY>
APP_PREVIOUS_KEYS=<YOUR_OLD_APP_KEY>

If Using docker-compose:

Update your docker-compose.yml:

version: "3.2"
services:
 input:
 image: ghcr.io/deck9/input:main
 volumes:
 - input-data:/var/www/html/storage
 ports:
 - 8080:8080
 restart: unless-stopped
 environment:
 - APP_URL=<YOUR_APP_URL>
 - APP_KEY=<YOUR_APP_KEY>
 - APP_PREVIOUS_KEYS=<YOUR_OLD_APP_KEY>

Step 4: Start the Container

If running the container directly, include the .env file:

docker run -d -p 8080:8080 --name input \
 -v input-data:/var/www/html/storage \
 --env-file .env \
 ghcr.io/deck9/input:main

Important

Setting APP_PREVIOUS_KEYS allows the application to migrate previously saved data, encrypting it with the new app key upon access.

Full Changelog: v1.9.2...v2.0.0

Contributors

PhilReinking
Loading

v1.9.2

21 Aug 16:25
@PhilReinking PhilReinking
673605e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

What's Changed

Full Changelog: v1.9.1...v1.9.2

Contributors

PhilReinking
Loading

v1.9.1

16 Aug 15:25
@PhilReinking PhilReinking
5568e71
This commit was signed with the committer’s verified signature. The key has expired.
PhilReinking Philipp Reinking
GPG key ID: 6872F2CDC0399726
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

  • Fixes dark appearance settings for file uploads
Loading

v.1.9.0

15 Aug 15:23
@PhilReinking PhilReinking
8c269fa
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.8.4...v1.9.0

Read about this release: https://getinput.co/changelog/v1-9-0-file-uploads

Contributors

anarion80, PhilReinking, and 5 other contributors
Loading

v1.8.4

18 Apr 15:14
@PhilReinking PhilReinking
e2343d9
This commit was signed with the committer’s verified signature. The key has expired.
PhilReinking Philipp Reinking
GPG key ID: 6872F2CDC0399726
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

Fixes authentication issues when docker container is running behind a proxy.

Full Changelog: v1.8.3...v1.8.4

Loading

v1.8.3

19 Mar 14:34
@PhilReinking PhilReinking
53ea1aa
This commit was signed with the committer’s verified signature. The key has expired.
PhilReinking Philipp Reinking
GPG key ID: 6872F2CDC0399726
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

What's Changed

Fixes

  • Changes default APP_URL to the value that is used in the docker build

New Contributors

Full Changelog: v1.8.2...v1.8.3

Contributors

mikeri and wesleysinks
Loading

v1.8.2

16 Feb 10:40
@PhilReinking PhilReinking
0f4f5db
This commit was signed with the committer’s verified signature. The key has expired.
PhilReinking Philipp Reinking
GPG key ID: 6872F2CDC0399726
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

  • Fixes migrations for the Sqlite driver

Full Changelog: v1.8.1...v1.8.2

Loading
ma-vo reacted with hooray emoji
1 person reacted

v1.8.1

20 Jan 12:12
@PhilReinking PhilReinking
3fe3108
This commit was signed with the committer’s verified signature. The key has expired.
PhilReinking Philipp Reinking
GPG key ID: 6872F2CDC0399726
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

Full Changelog: v1.8.0...v1.8.1

Loading

v1.8.0

13 Jan 00:38
@PhilReinking PhilReinking
f1e19f6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Choose a tag to compare

v1.8.0 Introducing Teams

Breaking Changes

In this release, we're introducing significant changes to our user model to enhance collaboration and streamline form management. We have shifted from allowing multiple separate user accounts to a unified team-based approach. This means all users on a single installation will now be part of one team, simplifying the process of managing forms collaboratively.

Important: When you upgrade to this version, the system will automatically transition all existing users to this new team-oriented architecture.

For those using the Self-Hosted version of Input, it's important to note that this update restricts the creation of multiple teams within a single installation. You will be able to set up one primary team and then invite users to this team through the Team settings.

If your current installation already has more than one user, we have avoided automatically merging these accounts into a single team to prevent any unintentional sharing of private data. Each existing user will initially be in separate teams. For users who wish to consolidate these accounts into a single team, please reach out for support. I can assist you with a script designed to safely merge these accounts into one team.

This change is a step towards making Input more collaborative and efficient for team-based form management. We appreciate your understanding and are here to assist with a smooth transition.

What's Changed

New Contributors

Full Changelog: v1.7.1...v1.8.0

Contributors

PhilReinking and Doskyft
Loading
Doskyft reacted with heart emoji
1 person reacted
Previous 1 3
Previous

AltStyle によって変換されたページ (->オリジナル) /