The Hot Updater
is designed to be highly customizable through its plugin system. This extensibility allows you to tailor the updater's behavior to fit your specific requirements.
The Build Plugin is used during the execution of the hot-updater deploy
command. Its primary function is to manage the build process for generating the required update bundles.
@hot-updater/metro
: Supports Metro bundler for React Native projects.@hot-updater/repack
: Coming soon.The Storage Plugin is utilized during the hot-updater deploy
command to upload bundles generated by the Build Plugin. It ensures that the update files are stored in a designated storage solution.
@hot-updater/supabase
: Provides supabaseStorage
functionality, leveraging Supabase for storage.@hot-updater/aws
: Provides s3Storage
functionality, enabling the use of AWS S3 for storage.The Database Plugin is responsible for storing the metadata required to check for updates. This plugin is activated during the execution of the hot-updater deploy
command.
@hot-updater/supabase
: Provides supabaseDatabase
functionality, using Supabase as a database solution.@hot-updater/aws
: Provides s3Database
functionality, utilizing AWS for database storage.@hot-updater/postgres
: Supports PostgreSQL for update metadata storage.Here’s an example of how to configure supabaseStorage
and supabaseDatabase
with environment variables for a seamless storage setup:
In this configuration:
supabaseUrl
: The base URL of your Supabase project, typically obtained from the Supabase dashboard.supabaseAnonKey
: The anonymous API key for accessing Supabase, also available in the dashboard.bucketName
: The name of the bucket where update bundles will be stored.By using environment variables, sensitive information is kept secure and can be easily managed across environments.