Profiles and web exports

Author education and publications

In My account → My profile card, enter the highest achieved EQF level,

degrees and qualifications (for example CSc., Ph.D. or DBA), academic rank

(associate professor/professor), school and field. The EQF level is not inferred

from degree suffixes. Czech examples: EQF 2 basic education, EQF 3 vocational

qualification with apprenticeship certificate, EQF 4 school-leaving examination,

EQF 5 professional qualification at level 5, EQF 6 higher vocational/bachelor,

EQF 7 master, EQF 8 doctoral education.

See Europass – EQF.

Add publications individually: title (required), year, publisher/journal and an

HTTP/HTTPS link, including a DOI URL such as https://doi.org/.... Edit or remove

entries and save the profile. Up to 100 publications are supported. Completed

education and publications are automatically public on an active public profile,

its JSON and vCard, without additional field-level disclosure switches. Revoking

the public profile consent hides the whole profile. Contact disclosure controls

still apply. Qualifications are self-reported, not verified by eUpdate.

Export a web project as an eWeb backup

Select Hosted website in project settings, for example with PHP technology.
Open Export for eWeb. Only the owner, their collaborators and an admin can

export. A SecretID does not grant this permission.

Choose a release, target domain without a protocol and the web directory inside

the package. . includes the entire package; web, public or dist includes

only that directory. Its contents map directly to /var/www/target-domain/web/.

Review the suggested directory derived from index.php/index.html. Frameworks

needing private files outside that directory require a separately prepared

deployment structure.

Download the ZIP and import it through eWeb backup restore.

The ZIP follows eweb-backup-v3: backup.json, data-www.tar.zst, readme.md

and SHA256SUMS. The web TAR contains only allowed roots web/, private/,

config/, logs/, cron/, never a top-level tmp/. It includes the selected

release files, basic domain configuration and newly generated account credentials.

No live database, separate modules, TLS keys or eUpdate service data are included.

Bundled SQL is a regular project file; the export does not import it into MySQL.

For a new domain, restore identity and files. Numeric UID/GID values are

allocated on the target; eWeb may report that the backup has no historical

identity. For an existing domain, restore files only to preserve its account,

password and settings. Restoring identity changes domain configuration and the

account password. File restoration replaces the existing web tree; back up the

live site first. The export stores a password in credentials.password_b64;

base64 is not encryption. Only its creator and admins can download the export.

Keep the downloaded ZIP private.

PHP is enabled when the selected directory contains PHP/PHTML files; the target

eWeb supplies the available PHP runtime. HTML and browser JavaScript are served

as static files. Export neither builds JavaScript nor configures Node.js services.

The eUpdate server needs Python 3, zstd and PHP proc_open. Limits: 30,000 files

and 2 GiB of unpacked data. The two latest backups per account are retained

locally, sharing the retention limit with other archive backups.

Project URLs and safe deletion

Open projects at /login/project, for example

https://update.estudium.eu/admin/eweb-server. Login is the owner account login,

not its display name or CORE; project is the project slug. Wrong owners and

missing projects return 404. Existing authentication and permissions still apply

to private projects. Old project.php?software_id=eweb-server links redirect

with HTTP 301. Cards, profiles, canonical metadata and sitemap use the new URL.

Changing the owner or login changes the pretty URL; the original software_id

link remains usable.

The supplied eWeb already routes through Nginx

try_files $uri $uri/ /index.php?$query_string;. index.php resolves the path,

so no hosting configuration or database password change is needed. Other hosts

must route missing paths to index.php while preserving REQUEST_URI. Reserved

config/private/backups/logs/tmp and _eweb_stats paths retain their system role;

colliding project paths use the legacy software_id URL.

The owner or administrator can select Delete entire project in project

settings and type its displayed identifier. Collaborators cannot delete it.

A backup must finish before deletion proceeds. Owners receive a project backup

with every version, module, statistics and licenses, excluding other account

data. Administrators retain the full archive backup workflow. Project backups

contain project.json and files; the bundled CLI restore handles full backups,

while project files can be uploaded again. Only the two newest backups per

creator are retained. Server check-in history is preserved.

To delete a release, type its version number, such as 1.2.3, without an

extra v prefix. The latest release date appears in a badge at the bottom left

of the project card. Account creation/editing errors appear at the bottom of

the account dialog.