jakim / ig-monitoring

🚨 DISCONTINUED🚨 IGMonitoring - Free, self hosted Instagram Analytics and Stats

🚨 IG Monitoring ends its way 🚨

The open source version will still be available on github, but will no longer be developed or actively supported.

IG Monitoring Cloud

Let me introduce you to a cloud version of a system I'm currently working on. Perhaps it will answer your needs. That will be more featured version of the system you know from GitHub, with more extensive tag analytics and account analytics expanded with locations. Additionally it'll have various permission levels, so you can create an account for a Client with stats available there. And that's just for a starter :)

Get your access here

Versions comparison

IG Monitoring - Free version

Screenshots

Free DEMO

Cloud Free Trial

Account statistics

Tag statistics

FAQ

PREMIUM SUPPORT

Versions comparison

Version

BETA stage. Use at your own risk.

Branch 0.9 is the most stable.

Installation

Before you start

You need WORKING proxies (at least 2). (I recommend the private, dedicated ones [aff link])

You need a server (vps will be ok) with linux, root access and configured LEMP, that is:

• php minimum 7.2
• latest nginx, recommended server configuration https://www.yiiframework.com/doc/guide/2.0/en/start-installation#configuring-web-servers
• mysql minimum 5.7 (or the appropriate mariadb, e.g. 10.3)
• installation instructions on Debian (there is no need for a firewall ;)

System installation (terminal)

• create database: mysql, utf8mb4
• run git clone https://github.com/jakim/ig-monitoring.git
• run cd ig-monitoring (you will enter the project catalog)
• download composer
• run php composer.phar install
• run chmod 0777 runtime
• run chmod 0777 web/assets
• run chmod 0777 web/uploads
• copy config/db.dist => config/db.php and enter the access data to the created database
• run php yii migrate (tables in the database should be created)
• run php yii admin/dictionaries

Configure google sign-in

• go to: https://console.developers.google.com and create a new project
• enable API: Google+ API
• add oAuth login credentials (type: web application)
• add authorized redirect url YOUR_DOMAIN/admin/auth/auth?authclient=google
• copy config/authClientCollection.php.dist => config/authClientCollection.php and enter clientId, clientSecret and redirectUrl as above

Worker configuration (data refreshing)

• install the supervisord, the method of installation depends on the system
• add configuration according to https://github.com/yiisoft/yii2-queue/blob/master/docs/guide/worker.md (in Debian 8 and 9: /etc/supervisor/conf.d/ig_monitoring.conf)
• change in the configuration:
  • user => nginx
  • numprocs => 2 is enough (I recommend twice less than the number of proxy and a number equal to the number of processor cores/threads)
  • I suggest stdout_logfile to be set to the project directory, ie PROJECT_FULL_PATH/runtime/logs/supervisor.log
• run supervisord
• add cron hourly for php /PROJECT_FULL_PATH/yii stats/update-accounts and php /PROJECT_FULL_PATH/yii stats/update-tags

Adding and activation of the system user

• try to log in, if everything goes well, you'll see an "inactive account message"
• run the command php yii user/activate 'YOUR_GOOGLE_EMAIL'
• log in again

Next steps

• add a few accounts and tags
• enjoy the system
• write a review
• tell your friends about the system
• star the project on github :)
• support the project by taking the cloud version

Legal

This code is in no way affiliated with, authorized, maintained, sponsored or endorsed by Instagram or any of its affiliates or subsidiaries. This is an independent tool. Use at your own risk.

Screenshots

FAQ

Why did I build it?

• Because I need something that I can quickly change for my needs.

Why is it free?

• Because I realized that I like building tools more than using them :)

Is it safe for usage?

• You never known, but I’m using this for few months now without any issue.

Do I need to enter my Instagram login and password?

• No, the system is based on publicly available data, so you do not have to provide any sensitive data.

Will the system harm my accounts?

• No, everyone can monitor public accounts.

Why did you build two versions?

• I needed a system to monitor accounts (now it's several thousands), but I enjoy software development more than accounts maintenance, which is why the free version was created. The cloud version was created as a response to all users problems with the installation and maintenance of the free version.

What do I expect from this share?

• New ideas would be great, feel free to create issue and PR. :)

Free Version PREMIUM SUPPORT

If you do not know how to get into the installation, I can do it for you. As part of the support, I offer:

• installation of a www server
• database installation
• script configuration
• free, good ssl certificate (letsencrypt)
• script modifications, according to requirements
• other software integration

Troubleshooting

'SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes

You probably have a low database version, make sure your system meets the requirements

ig-monitoring's Issues

too hard to install on windows

can u help? 🙉
after all just...

add the date of modification (on / off) of the monitoring and the possibility of sorting after it

It allows you to better check automatically added accounts

mark limited profiles on the list

https://www.instagram.com/bacardiusa/

Fix "method_lines" issue in modules/admin/controllers/AuthController.php

Method authSuccess has 34 lines of code (exceeds 25 allowed). Consider refactoring.

https://codeclimate.com/github/jakim/ig-monitoring/modules/admin/controllers/AuthController.php#issue_5a9af1d8d4e2800001000086

correct redirection after updating data from the pop-up

after create account monitoring, update account tags, etc.

possibility to export account media accounts

the ability to edit basic account values

• name
• username

automatic redirection, after logging in, to the proxy panel, if none has been added

display ER in the media accounts section

only if the account is monitored

update to Yii 2.0.14

account tagging does not work

create monitoring selects

update to yii 2.0.14.1

the ability to add to monitoring from the admin panel

• proxy alert
• monitoring/accounts
• account/media-accounts

like ./yii monitoring/account

account history

check if er is counted correctly

create a "media accounts" section in the tag profile

accounts from top 9 posts

add a link to the instagram page

maybe a small icon after username (global solution)

https://stackoverflow.com/questions/6817595/remove-http-referer

https://hidereferrer.com

http://www.whatismyreferer.com

track the number of likes in the past day, in the past 7 days & 14 days

It think the graph should have this added if possible
-The exact no of like in last day
-The Avg. no of like in the last 7 days - so it shouldn’t be based on last 10 posts, it should be based on how many post where made in the last 7 days
-The Avg no of likes in the last 14 days - same here

GET /accounts

GET /accounts (with the ability to send search parameters and/or datafilter)
#34

tags refactoring

better proxy support, the ability to choose an IP or group

Fix "method_lines" issue in modules/admin/components/grid/TagStatsColumn.php

Method getDataCellValue has 26 lines of code (exceeds 25 allowed). Consider refactoring.

https://codeclimate.com/github/jakim/ig-monitoring/modules/admin/components/grid/TagStatsColumn.php#issue_5a9af60f9af2770001000082

Test ticket from Code Climate

add update status

If the update returns an error, try to update the name, stop updating if unsuccessful.
after #32

GET /accounts/ID/media-accounts

GET /accounts/ID/media-accounts (with virtual attribute "occurs") and filtering options like #47
#34

account dashboard

public link for share account dashboard

use case: preview for the client

automatic tagging of discovered accounts with other tags than the main account

in the account settings
by default, the same tags as the main account

cache for data from instagram

change in ER accuracy to two digits

error page

main dashboard

Administrator notes

like tags

the ability to add search results to favorites

clear monitoring tabs

rm Locations (TODO)
rm Groups (TODO)

Migrations: Specified key was too long

Hi, I'm having problems when I start the initial migrations.

When I created the mysql database it does not have the option utf8mb4, but i have utf8mb4_bin, utf8mb4_general_ci, utf8mb4_unicode_ci and others.

I tried them all but they all give me the following error:

*** applying m180110_204953_create_account_table
    > create table account ...Exception 'yii\db\Exception' with message 'SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes
The SQL being executed was: CREATE TABLE `account` (
        `id` int(11) NOT NULL AUTO_INCREMENT PRIMARY KEY,
        `username` varchar(255) NOT NULL UNIQUE,
        `profile_pic_url` varchar(255),
        `full_name` varchar(255),
        `biography` varchar(255),
        `external_url` varchar(255),
        `instagram_id` varchar(255),
        `updated_at` datetime,
        `created_at` datetime,
        `monitoring` tinyint(1) NOT NULL DEFAULT 0
)'

in C:\xampp\htdocs\ig-monitoring\vendor\yiisoft\yii2\db\Schema.php:664

Error Info:
Array
(
    [0] => 42000
    [1] => 1071
    [2] => Specified key was too long; max key length is 767 bytes
)

Does anyone know how to help me?

thanks

better selection of the next proxy

choose wisely, not randomly

😄

the ability to delete the history of statistics

button in the account settings tab

github login

add support for the is_private flag for accounts

mark the icon on the list

Change label - "ER" to "Engagement rate" or "Engagement"

something more descriptive but short

import of accounts

auto change account name

after: jakim/ig#3

account notes do not work

the ability to change the account proxy settings

possibility to export account media tags

rest api

• standard implementation of yii2
• simple bearer token authorization
• codeception tests
• POST /accounts (a bit cheated, because if the username exists then it updates the existing account)
• GET /accounts (with the ability to send search parameters and/or datafilter) #47

IN PROGRESS

• GET /accounts/ID/media-accounts (with virtual attribute "occurs") #48

An idea for the next endpoints:

• GET /accounts/ID
• GET /accounts/ID/media-tags (with virtual attribute "occurs")
• GET /accounts/ID/stats

i can run only localhost

Dear,
i try to run as a web server (on LAN and over LAN) and nothing, i can run only local, there is a specific issue?
os: ubuntu 16.04LTS, php 7.25
regards

disable the "disabled" account flag, better analysis is needed

• the flag has not been removed.
• accounts with disabled = 1 are by default displayed at the beginning of the list
• added a command to reset the flag in all accounts