PHPackages natives/natives-core - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Admin Panels](/categories/admin) 4. / 5. natives/natives-core ActiveLibrary[Admin Panels](/categories/admin) natives/natives-core ==================== Kern voor beheerapplicaties van instrumentengids Eva 1.0.4(3y ago)012MITPHPPHP ^8.0 Since Mar 7Pushed 3y ago1 watchersCompare [ Source](https://github.com/NativesCloud/debug)[ Packagist](https://packagist.org/packages/natives/natives-core)[ RSS](/packages/natives-natives-core/feed)WikiDiscussions develop Synced 1mo ago READMEChangelogDependencies (18)Versions (3)Used By (0) Eva Laravel core ================ [](#eva-laravel-core) Setup ----- [](#setup) ### Installation [](#installation) To use this package in your own project run: `php artisan eva-core:install {--n|no-interaction}` Make sure you publish the config this package provides with: `php artisan vendor:publish` Besides config this package also offers translations and Open API specs ### Fresh instance [](#fresh-instance) Before setting up a new instance first make sure your .env file is setup. See .env variable descriptions below. When setting up a new instance of the project run: `php artisan eva-core:setup {--n|no-interaction}` This will freshly migrate the database and sets up some other services like the geo data. I recommend you create your own setup script which executes this script. ### Updating an existing instance [](#updating-an-existing-instance) When updating an existing instance of the project run: `php artisan eva-core:update {--n|no-interaction}`This will run missing migrations. I recommend you create your own update script which executes this script. Environment variables --------------------- [](#environment-variables) All .env variables used by the core are found in `.env.example`. Make sure to copy them to your own project's .env file APP\_DEDICATED\_INSTRUMENT\_TYPE : The name of the instrument type all instruments by default have ELASTIC\_INDEX\_PREFIX : The prefix used to prefix all elastic indeces ELASTIC\_CLOUD\_ID : The cloud id of the elastic search instance ELASTIC\_USERNAME : The username of the elastic search instance ELASTIC\_PASSWORD : The password of the elastic search instance ELASTIC\_PUBLIC\_CLOUD\_ID : The cloud id of the **public** elastic search instance - used to store data shared on kibana boards ELASTIC\_PUBLIC\_USERNAME : The username of the **public** elastic search instance - used to store data shared on kibana boards ELASTIC\_PUBLIC\_PASSWORD : The password of the **public** elastic search instance - used to store data shared on kibana boards FILESYSTEM\_STORAGE\_PATH\_DOWNLOADS FILESYSTEM\_DIRECTORY\_PATH\_DOWNLOADS : The directory where all files from the download entities are stored AWS\_ACCESS\_KEY\_ID : AWS Access key for S3 filesystem settings AWS\_SECRET\_ACCESS\_KEY : AWS Secret access key for S3 filesystem settings AWS\_REGION : AWS region for S3 filesystem settings - defaults to `eu-central-1` AWS\_URL : AWS url for S3 filesystem settings AWS\_BUCKET : AWS bucket name for S3 filesystem settings AWS\_BUCKET\_GEO : AWS bucket name for storing geo data on S3 filesystem settings AWS\_SDK\_ACCESS\_KEY\_ID : Thw AWS acces key id for AWS cognito service API calls AWS\_SDK\_SECRET\_ACCESS\_KEY : Thw AWS acces key for AWS cognito service API calls AWS\_SDK\_REGION : defaults to `eu-central-1` CLI Commands ------------ [](#cli-commands) This package offers a number of CLI commands. You can find their description in their classes Geo Data -------- [](#geo-data) Eva uses geo data from townships and labor market regions. There are various API's that can be used as the source for this data. We use the API data to generate a source file. This source file is the single point of truth we use to create our database entries. There are various commands to check if the source file or database is up-to-date and other commands to update them if they're not. ### New source and new data set [](#new-source-and-new-data-set) To generate a new township and region source run ``` php artisan geo:generate-source ``` You can also generate a new source for either townships or regions. Without the `--update-source` option you create a new source snapshot. Run it, check the file, and when satisfied add the option to overwrite the source file. ``` php artisan geo:townships-create-dataset {--update-source} php artisan geo:regions-create-dataset {--update-source} ``` You can create townships and regions from the source file with the following commands. These commands are not careful. They will create or update the data but they will not check if current entries don't exist anymore and the items associated with them need reallocation. So not recommended with an existing data set. ``` php artisan geo:townships-create php artisan geo:regions-create ``` ### Existing source or existing data set [](#existing-source-or-existing-data-set) Once you have your data established you want to monitor for changes. To do this you can run the following commands. These will only show the missing items between multiple API's and the data source. #### Check for deviations between API and Source [](#check-for-deviations-between-api-and-source) ``` php artisan geo:townships-check-source-from-api php artisan geo:regions-check-source-from-api ``` #### Snapshot creation for manually checking source set [](#snapshot-creation-for-manually-checking-source-set) We currently use the Cbs Open Data Api to create the source file. When checking for changes in the various API results, look for that one. Create data snapshot and check them in storage under fixed/area ``` php artisan geo:townships-create-dataset php artisan geo:regions-create-dataset ``` #### Update the Source file with the data from the API [](#update-the-source-file-with-the-data-from-the-api) When your happy with the snapshot, run it again with the `update-source`option. ``` php artisan geo:townships-create-dataset --update-source php artisan geo:regions-create-dataset --update-source ``` #### Check for deviations between Source file and Database [](#check-for-deviations-between-source-file-and-database) You can also check if the database is up to date with the source data. The following commands will check for missing items and content deviations. ``` php artisan geo:townships-check-data-from-source php artisan geo:regions-check-data-from-source ``` #### Update the Database with the data from the Source file [](#update-the-database-with-the-data-from-the-source-file) When you decide to update the database with the source data you can run the update commands. These commands will show you each deviation and offers you the choice to update the data. Before you run this you want to have checked all the changes between the source and the database and want the source in a state in which you can just answer yes to all the changes. ``` php artisan geo:townships-update-data-from-source php artisan geo:regions-update-data-from-source ``` > ***NOTE:*** Some deployment methods might not allow for interaction. In that case you can run the commands with the yes-to-all flag. Do make sure to check the deviations before running the command ``` php artisan geo:townships-update-data-from-source --yes-to-all php artisan geo:regions-update-data-from-source --yes-to-all ``` Package contents ================ [](#package-contents) - Casts which can be used to cast model properties to a format - CLI Commands - Elastic resources for mapping database data to elastic documents - Enums which provide static options for some model properties - Events which are mostly used to trigger data to elastic search synchronisation - Http requests used in the repositories to enforce validation rules - Http resources which can be used in API reponses - Http validation rules which are used in the requests to enforce correct user input - Interfaces - Jobs, mostly used for elastic synchronisation / management tasks - Listeners for the events - Models - Notification messages - Observers - Policies - Providers - Repositories which can be used for storing / retrieving model entities - Services, various business logic services - Traits Professionals ------------- [](#professionals) When creating a professional, a user is created in Amazone Cognito. These are users for the instrument catalog. The data in the professionals' table is a copy of the users in the cognito user pool. The data from the id-provider is leading To sync the data in the database with the data from the id-provider you can run the following command. ``` professionals:sync {environmentSlug?} {--d|destructive} ``` The commands updates the last\_seen\_date of all the professionals it found. Naturally the last\_seen\_date of professionals missing from the id-provider will not update. You might want to remove those from professionals from the database. You can use the destructive option to do so ### Health Score 23 — LowBetter than 27% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity5 Limited adoption so far Community9 Small or concentrated contributor base Maturity51 Maturing project, gaining track record Bus Factor1 Top contributor holds 99.1% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 1166d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/479ae0f0fd90d0c3797537055e6b95000fa1800731d2c0bb962edb097b544ae6?d=identicon)[NativesCloud](/maintainers/NativesCloud) --- Top Contributors [![waotaa](https://avatars.githubusercontent.com/u/1527800?v=4)](https://github.com/waotaa "waotaa (105 commits)")[![jessevanmuijden](https://avatars.githubusercontent.com/u/2759225?v=4)](https://github.com/jessevanmuijden "jessevanmuijden (1 commits)") --- Tags coreevavnginstrumentengids ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/natives-natives-core/health.svg) ``` [![Health](https://phpackages.com/badges/natives-natives-core/health.svg)](https://phpackages.com/packages/natives-natives-core) ``` ### Alternatives [bagisto/bagisto Bagisto Laravel E-Commerce 26.2k161.6k7](/packages/bagisto-bagisto)[backpack/crud Quickly build admin interfaces using Laravel, Bootstrap and JavaScript. 3.4k3.4M207](/packages/backpack-crud)[krayin/laravel-crm Krayin CRM 22.0k32.8k1](/packages/krayin-laravel-crm)[unopim/unopim UnoPim Laravel PIM 9.4k1.8k](/packages/unopim-unopim)[blair2004/nexopos The Free Modern Point Of Sale System build with Laravel, TailwindCSS and Vue.js. 1.2k2.3k](/packages/blair2004-nexopos)[eveseat/web SeAT Web Interface 2723.2k135](/packages/eveseat-web) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)