Product: SkyTechNG Alumni Portal
Developer: SkyTechNG
Installation method: Web-based installer
Recommended hosting: cPanel shared hosting or a compatible PHP hosting environment

1. Introduction

The SkyTechNG Alumni Portal is a web-based alumni association management system designed to help organizations manage members, dues, finances, donations, events, projects, welfare activities, elections, and communication from one centralized platform.

This guide explains how to install the portal on a new domain or subdomain using the fresh-installation ZIP package.

Important: Use the fresh-installation package for a new deployment. Do not use an incremental update ZIP to install the application on a new domain.

2. Server Requirements

Before installation, ensure that your hosting account meets the following requirements:

• PHP 8.3 or later, compatible with the supplied application.
• MySQL or a compatible MariaDB database.
• PHP PDO MySQL support.
• PHP OpenSSL extension.
• PHP Mbstring extension.
• PHP XML extension.
• PHP Fileinfo extension.
• PHP HTTPS stream-wrapper support and allow_url_fopen enabled for online licence activation.
• Composer dependencies included in the installation package.
• Writable application storage and bootstrap/cache directories.
• HTTPS enabled through a valid SSL certificate.
• SSH or cPanel Terminal access recommended for running Artisan commands.

Your hosting provider may need to enable the required PHP extensions.

1. Prepare Your Domain
2. Log in to your cPanel account.
3. Create or select the domain or subdomain where you want to install the portal.
4. Ensure the domain points to the correct application directory.
5. Enable SSL and confirm that the domain loads over HTTPS.

For a root-directory deployment, the application files should be placed in the directory containing index.php, .htaccess, artisan, and composer.json.

Do not point the domain to a separate /public directory unless the supplied package specifically requires that configuration.

1. Create a MySQL Database
2. Open MySQL Database Wizard in cPanel.
3. Create a new database.
4. Create a dedicated database user.
5. Assign the user to the database.
6. Grant the privileges required by the application, including table creation and modification.

Record the following information:

• Database name
• Database username
• Database password
• Database host, normally localhost on cPanel hosting

Use the complete database name and username, including any cPanel account prefix.

Important: Use an empty database for a fresh installation. Do not import a production database backup or an existing alumni association’s records into the new installation.

1. Upload and Extract the Installation Package
2. Download the official SkyTechNG Alumni Portal fresh-installation ZIP.
3. Open File Manager in cPanel.
4. Navigate to the document root of your selected domain.
5. Upload the ZIP file.
6. Extract the archive into the domain’s application directory.
7. Confirm that the application files and folders are in the correct location.

The directory should contain the installation files, including installer.php, artisan, composer.json, vendor, index.php, and .htaccess.

If the archive extracts into a nested folder, move the application files into the intended directory before continuing.

Do not upload the incremental update package in place of the fresh-installation package.

6. Start the Web Installer

Open the following address in your browser:

https://your-domain.com/installer.php

Replace your-domain.com with your actual domain.

The installer should display its system requirements and configuration steps.

If the installer reports a missing PHP extension, an unsupported PHP version, or a directory permission problem, correct the issue before proceeding.

7. Activate Your Product License

Enter the valid SkyTechNG Alumni Portal license key when prompted.

The installer contacts the configured SkyTechNG license server to validate and activate the license for your installation.

Ensure that:

• Your hosting account can make HTTPS requests to the licence server.
• Your license is valid for the product and domain.
• The domain is entered correctly.
• Your hosting environment supports the required TLS certificates and HTTPS connections.

Do not share your license key publicly.

8. Configure the Database

Enter the database details created in Step 4:

• Database host
• Database name
• Database username
• Database password

The installer should test the database connection before proceeding.

If the connection fails, verify the database credentials, database privileges, and database host.

Do not continue until the connection succeeds.

9. Create the Initial Administrator Account

Complete the administrator account form using the requested information, such as:

• Administrator’s name
• Email address
• Password
• Password confirmation

Use a strong, unique password. Avoid using a password shared with your hosting account or other services.

Keep the administrator credentials in a secure password manager.

10. Complete the Installation

After the required information has been accepted, the installer should:

1. Generate the application’s environment configuration.
2. Generate the Laravel application encryption key.
3. Save the database configuration.
4. Run the required database migrations.
5. Seed the initial application data where configured.
6. Create or configure the initial administrator account.
7. Store the license information.
8. Create the installation lock to prevent the installer from being run again.

Wait for the installer to report successful completion before opening the administration dashboard.

11. Configure the Update Signing Public Key

The SkyTechNG Alumni Portal requires the trusted update signing public key to verify signed software updates.

The following setting must be present in the application’s .env file:

SKYTECHNG_UPDATE_PUBLIC_KEY=npvz1krvuHEQMv+6+43ZSFFrQn2QRXA2SxEXpfBcafk=

The key should be included automatically in future fresh-installation packages. If it is missing, open the .env file in the application root and add the setting above.

After changing the environment configuration, clear Laravel’s configuration cache from the application root:

php artisan optimize:clear

This public key must match the key used by the update server to verify release signatures. Never put the signing private key in the application installation. 

12. Secure the Installation

After the installer reports success:

1. Delete installer.php from the application directory.
2. Confirm that the installation lock has been created.
3. Keep .env protected from public access.
4. Ensure that application storage and cache directories have appropriate permissions.
5. Keep APP_DEBUG=false in production.
6. Confirm that HTTPS is working.
7. Use strong administrator credentials.
8. Back up the database and application files.

Do not make the entire application directory writable by everyone. Use the minimum permissions required by your hosting environment.

13. Configure Email and SMTP

Configure the portal’s email settings using your authorized SMTP provider.

Enter the appropriate SMTP host, port, encryption method, username, password, and sender details.

Send a test email to confirm that delivery works.

Email configuration is important for administrator notifications, member communication, and mass-mail campaigns.

For larger mailing campaigns, confirm that your SMTP provider’s sending limits permit your intended volume.

14. Configure Payment Gateways

If your association intends to collect online dues or donations, configure the supported payment gateway in the portal’s settings.

Enter the required API credentials and configure the appropriate currency and transaction options.

Use test or sandbox credentials first where the payment provider supports them. Verify successful payments, failed payments, transaction records, and confirmation notifications before accepting live payments.

Payment gateway availability depends on the integrations included in your package.

15. Configure Scheduled Tasks (Cron Jobs)

If the portal uses Laravel’s scheduler for automated tasks, configure the scheduled command through cPanel’s Cron Jobs section.

A typical command is:

* * * * * cd /home/CPANEL_USERNAME/DOMAIN_DIRECTORY && /usr/local/bin/php artisan schedule:run >> /dev/null 2>&1

Replace the example path with the actual application directory on your hosting account and use the correct PHP CLI executable for your server.

The portal’s Settings page may provide cron job instructions. Always verify that the generated command reflects your current installation rather than a previous domain.

The scheduler must run at the required interval for scheduled tasks to execute reliably.

16. Test the Installation

Before making the portal available to members, verify the following:

• The homepage loads correctly.
• The administrator can sign in and sign out.
• Member registration and login pages work.
• Membership records can be created and viewed.
• Dues and financial pages load correctly.
• Donations and fundraising pages work where enabled.
• Event and project management pages load.
• Welfare and election features work where configured.
• SMTP test emails can be delivered.
• Payment gateway tests succeed where configured.
• Cron job instructions show the correct domain and application path.
• The update page recognizes the trusted signing public key.
• The system update service can retrieve and verify a correctly signed release.

If a page returns a server error, inspect the Laravel log at storage/logs/laravel.log and resolve the underlying issue before proceeding. 

17. Backup and Maintenance

Establish a regular backup schedule for the database and application files.

Before applying any software update:

1. Back up the database.
2. Back up the application files and environment configuration.
3. Confirm that the update package matches the product and release version.
4. Apply the update using the supported update mechanism.
5. Run any required migrations.
6. Clear cached configuration if necessary.
7. Test the important application functions.

Never use php artisan migrate:fresh on an existing installation, because it drops existing tables and can destroy application data.

18. Troubleshooting

The installer does not open.
Check the domain’s document root, PHP version, .htaccess, file permissions, and PHP error logs.

The database connection fails.
Confirm the database name, username, password, host, and user privileges.

The application returns a 500 Server Error.
Inspect storage/logs/laravel.log and identify the exact exception. Clear Laravel’s caches after appropriate configuration changes. 

The update page reports that the signing public key is missing or invalid.
Verify that SKYTECHNG_UPDATE_PUBLIC_KEY is present in .env, that the value is correct, and that Laravel’s configuration cache has been cleared.

A page reports that a database table does not exist.
Check the migration status and apply the required migrations using php artisan migrate –force after taking a backup.

Cron jobs use an old domain or directory.
Check the generated command and replace any hard-coded paths with the actual cPanel username and application directory.

19. Installation Completion Checklist

Before launching the portal, confirm that:

• The domain and SSL certificate work correctly.
• The application is installed in the intended directory.
• The product license is activated.
• Database migrations completed successfully.
• The initial administrator can sign in.
• The update signing public key is configured.
• installer.php has been deleted.
• Email settings have been tested.
• Payment settings have been tested where applicable.
• Cron jobs use the correct application path.
• Important pages and features have been tested.
• Backups have been configured.

Support

For installation assistance, provide your hosting environment details, the exact error message, and the relevant application log entries to the SkyTechNG technical support team. Never include passwords, private API credentials, or license secrets in public support requests.

SkyTechNG Alumni Portal — Empowering alumni associations through organized administration, transparent financial records, stronger connections, and collaborative development.