Interview Task: Fix-519 docker image cleanup#581
Conversation
…pp_api into fix-519-docker-image-cleanup
|
Good day.
It is from the server repo, here are the docs for it.
What permissions errors do you have accessing this? We usually use this perfect repo for easy installing dev setups. It has documentation how to enable debugging, and it is possible to debug background jobs. |
Thank you for the info. I will go over it again. |
Interview Task Report https://github.com/nextcloud/app_api/issues/519
From my understanding, the app_api codebase is mainly a devOps tool used for managing other applications
I've struggled with getting the app up and running. I followed the documentation here: https://docs.nextcloud.com/server/latest/developer_manual/exapp_development/index.html
While following the documentation, I couldn't find the script that this command executes:
./occ app:enable --force app_apiPerhaps this is in theservercodebase instead? if that's the case, it isn't clear in this documentationI However, did manage to get the environment up and running at http://nextcloud.local using the
docker-socket-proxyrepository.Solution
It took my quite some time to understand the codebase, but I managed to have a fair idea of it
In the
libfolder, I introduced the following method in.../lib/DeployActions/DockerActions.phpThe aim is to call docker's/images/pruneAPINext, I implemented the following
lib/BackgroundJob/DockerImageCleanupJob.phpWith these in place, I am struggling to understand how they tie into the entire nextcloud ecosystem and how to actually debug the code to see it in action.
this is because with the development environment running, and after I login, I couldn't access
http://nextcloud.local/index.php/settings/admin/app_apidue to permission issues.With this, exploration, I need help with some more concrete walkthrough of the codebases and how they work together and to understand how to properly introduce my changes and test them.